Data types
This page defines all shared types referenced by the Verify API and Compute API endpoints.Input
All compute endpoints accept geometry inputs as a discriminated union. The server resolves the input format automatically.The SDK accepts bare UID strings (e.g.,
"0xabc123...") and normalizes them to OnchainInput before sending to the API. When calling the API directly, always use the { uid: string } object form.RawGeometryInput
A standard GeoJSON geometry object:OnchainInput
A reference to an onchain EAS attestation:OffchainInput
A reference to an offchain attestation stored on IPFS or another URI-addressable store:VerifiedProofInput
A previously verified location proof, used to chain proof verification with compute operations. Pass the fullVerifiedLocationProofResponse object returned by POST /verify/v0/proof:
LocationClaim
A claim that a subject was at a location during a time window. Extends Location Protocol v0.2.LocationStamp
Evidence from a single proof-of-location system — one observation. Uses LP format for the observed location.LocationProof
A claim bundled with one or more stamps.SubjectIdentifier
Identifies the subject of a claim. Follows a scheme/value pattern similar to DIDs.Signature
A cryptographic signature on a stamp.CredibilityVector
Multidimensional assessment of how well stamps support a claim. Returned by POST /verify/v0/proof.StampResult
Per-stamp verification result within aCredibilityVector.
AttestationData
EAS attestation data returned by compute endpoints.The verify proof endpoint returns an extended attestation that also includes
uid, time, expirationTime, and revocationTime. See VerifiedLocationProofResponse for details.