StillMine

StillMine for developers

Add image claims to your app

Your users stay in your product. Send fingerprints from your server and receive permanent public certificate links—StillMine handles the claim records and Bitcoin anchoring.

Add StillMine to your Base44 prompt

Paste your app prompt. We'll keep your idea and add the API, backend and secure key setup StillMine needs.

0/8000 · sign-in required

One integration, two app types

A single-owner app can use its business name for every claim. A multi-user app sends a different user_ref and owner_name for each member—those members do not need StillMine accounts.

1. Create a business

Get one private API key for your app in the Business Portal.

2. Identify your user

Send your own stable user ID as user_ref and their display name as owner_name.

3. Save the proof link

Show the returned certificate URL beside the image in your app.

Get an API key

Multi-user marketplace example

Let each member claim their own work

Compute the two fingerprints in your app, send them to your own server, then call StillMine from there. Store the returned link in your database so each member sees their proofs in your existing dashboard.

// Run on your server — never in browser code
const response = await fetch(
  "https://still-mine-proof.base44.app/functions/registerClaim",
  {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      "X-API-Key": "<your API key, loaded from your server's secret store>"
    },
    body: JSON.stringify({
      user_ref: currentUser.id,
      owner_name: currentUser.shopName,
      filename: image.name,
      sha256: image.sha256,
      phash: image.perceptualHash,
      width: image.width,
      height: image.height
    })
  }
);
const claim = await response.json();
const proofUrl = "https://stillmine.me" + claim.certificate_url;
// Save proofUrl with the user's image record.

Keep the API key server-side. The browser may calculate fingerprints, but it should send them to your backend. Never place the key in frontend JavaScript or a mobile app bundle.

API reference

Use the base URL https://still-mine-proof.base44.app. All hashes are lowercase 64-character hexadecimal strings.

POST/functions/registerClaim

Create one claim. Requires X-API-Key and user_ref.

POST/functions/bulkClaims

Create up to 20 claims. Requires X-API-Key.

POST/functions/verifyImage

Public exact or similar-image lookup. No key required.

Single-claim response

{
  "id": "claim_record_id",
  "slug": "a1b2c3d4e5",
  "certificate_url": "/claim/a1b2c3d4e5",
  "ots_status": "pending_bitcoin",
  "existing": false
}

Requests are idempotent per business and exact SHA-256: sending the same file again returns its existing certificate.

Verification & registry check

Verify lookups are free. Compute all three fingerprints on-device — the photo never uploads.

POST https://still-mine-proof.base44.app/functions/verifyImage
{ "sha256": "<cleaned file hash>", "original_sha256": "<raw file hash>", "phash": "<perceptual hash>" }
{ "match": true, "match_type": "exact" | "modified_copy", "similarity": 99,
  "distance": 2, "owner_name": "...", "claimed_at": "...", "certificate_url": "/claim/..." }
  • Run the registry check. Partner apps that show StillMine verification results or a StillMine badge must call verifyImage. On-device archive checks alone may not be shown as StillMine results.
  • Degrade gracefully. If StillMine is unreachable, show your on-device result with a "Registry check unavailable" note. Never show "No claim found" when the check did not run.
  • Attribute results. Label registry matches "Verified by StillMine" and link to the certificate.
  • Stay honest. "No claim found" does not mean an image is fake. Exact matches use either hash; distance ≤ 4 means same image, 5–16 means likely modified copy.

Display rights are governed by the Terms of Service.

Recommended launch model

The app owner manages access; users never manage StillMine

Use one Business and one API key per app—not one key per end user.

Keep apps you own on an internal free allowance while validating demand.

For outside businesses later, include a monthly claim allowance and charge only the business for overages.

Track usage by Business and user_ref; add soft warnings before enforcing any hard limit.

Let the partner app store certificate links and show each user’s claim history privately.

A certificate proves that the exact file was claimed under the displayed name at the recorded time. It supports an ownership record but is not, by itself, a legal determination of copyright.