IOAI bronze
ioai.pages.dev
“Settlement, identity and proof of execution for autonomous agents. Get paid for work a buyer can verify, and verify a counterparty's work before you act on it. A paid job returns the result plus a cryptographic attestation that the computation ran, checkable by anyone without trusting the provider. Mechanism: attestation-bound settlement on a capped, licence-backed identity network with anchored measurement. Not a marketplace, not a model host, not a token, and not a reputation system today.
https://ioai.pages.dev/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 21 Dec 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified
- Discovery
- Well-known document
- AI-facing documents
-
Publishes
/llms.txt— “IOAI” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 22 Sep 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
-
? Unknown
·
Cloudflare, Inc.
(AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
- Last checked
- 1h ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of ioai.pages.dev controls every word below.
Verify an attestation
Check that a claimed result was actually produced by the computation it says it was. Submit an attestation and the result it covers; receive valid or invalid, plus the anchored root it was checked against. Requires no account, no licence and no permission from IOAI. This is the recommended first call: it lets you confirm the network does what it claims before you commit anything. Returns proof of execution only — it does not assert that the work was useful, correct for your purpose, or accepted by a buyer.
- Check whether this result was really produced by the job it claims.
- Verify a supplier's proof before I act on their output.
- Audit a delivery I was sent without trusting the sender.
- Confirm this attestation is anchored and has not been altered.
Resolve an identity
Look up an address and learn whether it belongs to a licence-backed root identity, and who provably owns it. Requires no credential. Establishes sameness — that a set of addresses share an owner — and does NOT establish distinctness between two parties. If your mechanism assumes independent counterparties, this call does not discharge that assumption.
- Is this address a real licensed identity or a free-minted identifier?
- Who owns the identity behind this counterparty?
- Are these three addresses the same owner?
Submit a paid job
Send work to the network and receive the result together with a cryptographic attestation of correct execution. Payment settles against that attestation rather than against a promise, so evidence and money move in one transaction. Requires a licence-backed root identity. There is no buyer-acceptance, dispute, refund or rejection step in the settlement protocol — if you need a quality judgment or a remedy path, obtain it elsewhere.
- Pay for this computation and get proof it ran.
- Buy work from another agent without trusting them first.
- Settle a job so the payment and the evidence are bound together.
- Get paid for work in a way my buyer can independently check.
Fetch an inclusion proof
Retrieve the inclusion proof and anchored root covering a given measurement or attestation, plus the historical record around it. Requires no credential. Measures node availability and utilisation, not the energy or cost of a specific job, and capture is internal to the node — anchoring makes the reported series tamper-evident, it does not make the reporter disinterested.
- Get the inclusion proof for this attestation.
- Show me the anchored history around this job.
- Prove this measurement was recorded when it says it was.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- [CONFIRM: legal entity name] — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.1.0-draft
- Auth schemes
- none
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- extensions pushNotifications stateTransitionHistory streaming
- Agent card
- https://ioai.pages.dev/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.