spoofsense.ai valid
SpoofSense
Face liveness and deepfake detection API
- Authority
- 50 reach 0 · trust 10 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://docs.spoofsense.ai/llms.txt
- llms-full.txt
- https://docs.spoofsense.ai/llms-full.txt
- Sections
- 1
- Links
- 24
- Size
- 4987 bytes
- Registered
- 2022-03-16
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T18:52:04.008Z
- Last checked
- 2026-10-25T18:52:06.152Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T18:52:04.016Z. Cached copy · Source on spoofsense.ai
# SpoofSense
> Face liveness and deepfake detection API
- [Introduction](https://docs.spoofsense.ai/index.md): Face liveness and deepfake detection, behind one API
- [Quickstart](https://docs.spoofsense.ai/quickstart.md): Your first liveness check in five minutes
- [Authentication](https://docs.spoofsense.ai/guides/authentication.md): Secret keys and session tokens
- [Image inputs](https://docs.spoofsense.ai/guides/image-inputs.md): Every way to send an image to the detection endpoints
- [Deepfake signals](https://docs.spoofsense.ai/guides/deepfake-signals.md): Content Credentials, the two deepfake detectors, and how to read the breakdown
- [Thresholds & scores](https://docs.spoofsense.ai/guides/thresholds.md): How genuine_score and decision work, and when to tune the threshold
- [Credits & billing](https://docs.spoofsense.ai/guides/credits.md): What a call costs and how balances behave
- [Errors](https://docs.spoofsense.ai/guides/errors.md): Every error code, and what to do about it
- [How sessions work](https://docs.spoofsense.ai/verification-sessions/overview.md): The secure capture flow behind the SDKs and hosted page
- [Web SDK](https://docs.spoofsense.ai/verification-sessions/web.md): Camera capture for browsers — React, vanilla JS, or a script tag
- [Android SDK](https://docs.spoofsense.ai/verification-sessions/android.md): Native capture with CameraX and Play Integrity signals
- [Hosted verify page](https://docs.spoofsense.ai/verification-sessions/hosted.md): Zero frontend code — redirect or embed our capture page
- [Results & media](https://docs.spoofsense.ai/verification-sessions/results.md): Reading the decision and retrieving the captured selfie — server-side
- [Face liveness check](https://docs.spoofsense.ai/api-reference/detection/face-liveness-check.md): Checks whether the face in the image is a live capture rather than a presentation attack (printed photo, screen replay, mask). Costs 1 credit.
- [Deepfake check](https://docs.spoofsense.ai/api-reference/detection/deepfake-check.md): Checks whether an image is AI-generated, and whether the face in it has been manipulated (face swap, AI edit, lip-sync, reenactment). C2PA Content Credentials are checked first: a valid credential saying the image was made or edited with AI flags it without running the models. Otherwise both detecto…
- [Liveness + deepfake in one call](https://docs.spoofsense.ai/api-reference/detection/liveness-+-deepfake-in-one-call.md): Runs both checks on the same image. The overall `decision` is `real` only when every check passes its threshold; per-product outcomes are in `checks`. Costs 3 credits.
- [Create a verification session](https://docs.spoofsense.ai/api-reference/verification-sessions/create-a-verification-session.md): Called from your backend with the secret key. Mints a single-use `sst_` client token — returned exactly once, only its hash is stored. Products and thresholds are fixed here, server-side; the client can never change them. Fails fast with 4
…Machine-readable: GET /v1/resolve?q=spoofsense.ai · GET /v1/domain/spoofsense.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage spoofsense.ai, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for spoofsense.ai:
1. POST https://agentwebmap.com/v1/sites/spoofsense.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://spoofsense.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/spoofsense.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/spoofsense.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.