Verify proof
Verify a location proof (a claim bundled with one or more stamps). This endpoint verifies each stamp individually, then cross-correlates them to produce a CredibilityVector — a multidimensional assessment of how well the evidence supports the claim.The Verify API does not return a single summary score. The
CredibilityVector provides spatial, temporal, validity, and independence dimensions so your application can define its own trust model.Request body
LocationProof
required
The proof to verify. Contains a
claim (LocationClaim) and an array of stamps (LocationStamp).number
Chain ID for EAS attestation signing (e.g.,
84532 for Base Sepolia).boolean
Whether to submit the attestation onchain. Defaults to
false.Example request
Response
The response contains the verified proof, a credibility vector, and optional EAS attestation data.LocationProof
required
The verified proof object.
CredibilityVector
required
Multidimensional assessment of how well the stamps support the claim. See CredibilityVector for the full type.
string
required
The evaluation method used (e.g.,
"multifactor-v0").number
required
Unix timestamp (seconds) of when the evaluation was performed.
AttestationData
EAS attestation data. Present when
chainId is provided. See AttestationData.DelegatedAttestationData
Delegated attestation for onchain submission. See DelegatedAttestationData.
Example response
Credibility vector
Thecredibility field is a CredibilityVector with four dimension groups:
dimensions.spatial
How close each stamp’s observed location is to the claimed location.
dimensions.temporal
How well each stamp’s temporal footprint overlaps with the claimed time window.
dimensions.validity
Fraction of stamps passing each verification check.
dimensions.independence
How independent and corroborative the evidence sources are.
stampResults
Per-stamp verification results. See StampResult for the full type.
meta
Errors
Errors follow RFC 7807:SDK: Location proofs
See the SDK documentation for client-side usage