Lexicon Garden

dev.cocore.compute.verifySettlement

Verify an indexed settlement against its receipt and the requester's payment authorization: confirms the settlement chain is internally consistent and signed by the settling repo. Returns the verification verdict plus any findings.

Repository @cocore.dev did:plc:5quuhkmwe2q4k3azfsgg7kdz namespace authority
Details · query
Kindquery
Authoritycompute.cocore.dev
Indexed
Compare Edit in builder → Fork →

Query

query · GET

Parameters

query string

uri

requiredstring · at-uri

The settlement record URI to verify.

Output

application/json

findings

requiredarray
itemsref
Reference

ok

requiredboolean

Errors

InvalidRequest

The `uri` parameter is missing.

NotFound

The settlement, or its referenced receipt/authorization, is not indexed.

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • dev.cocore.compute.verifyReceipt

    query

    Verify an indexed receipt offline-equivalently: structural checks against its job + attestation, a P-256 ECDSA signature check of `enclaveSignature` against the attestation public key, lexicon-schema validation, and — when an MDA cert chain is present — a hardware-attestation check bound to the signing key. `trustLevel` rises to `hardware-attested` only when a valid Apple chain certifies the receipt-signing key.

  • dev.cocore.compute.listSettlements

    query

    Indexed `dev.cocore.compute.settlement` records (capped at 200), optionally filtered by the settled receipt URI and/or the requester DID (matched against the authorization URI prefix).

  • network.attested.verify

    query not from the namespace authority

    Verify the attestations on a record. Resolves the record at `uri`, recomputes the canonical attestation CID, and checks each entry in its signatures array: inline network.attested.signature entries are verified by ECDSA against `key`; remote strongRefs are resolved to network.attested.proof records whose `cid` must match the subject's canonical CID. Any network.attested.* speaker can call this to verify without re-deriving the CID machinery.