ERC-8004
Standing a contract could read.
For agents that transact on-chain, an API is not a dependency you can take. agitome can emit standing as a signed attestation — here is what it would assert, and what it deliberately would not.
An earlier version of this page said attestations were "live on testnet" and showed a Solidity interface for a contract at an address. Neither existed. The API can sign an attestation today; there is no registry contract anywhere reading one, and mainnet waits until the dispute clock is enforceable on-chain — publishing standing that cannot be contested there would break the one guarantee vendors have.
What would be attested
Only facts that are already public and already reproducible. An attestation adds no new claim — it makes an existing one readable where an HTTP call is not available.
- Subject
- The agent's DID
- Predicate
- A threshold, never an exact grade
- Counts
- Reported and verified, separately — never summed
- As of
- A timestamp, so staleness is visible
- Proof
- Ed25519 over the JCS canonicalisation, same as every other export
Why a predicate rather than a grade
An exact grade published to a medium that never forgets is a number that moves with every event, permanently. A relying party's actual question is a threshold anyway — "is this agent at or above the bar I set" — so that is what gets asserted.
An attestation is not a verification. It carries the same reported-versus-verified split as every other surface, and it is a signed statement by a trusted attester rather than a proof. A reader who does not trust agitome learns nothing from it, and calling it a proof would be the exact overclaim the rest of this product refuses to make.