Agent’s-Eye View
What an AI agent actually sees when it meets a Presence on Place & Space.
Everything below is generated from the same machine-facing surfaces an autonomous agent uses — the A2A AgentCard, the answer summary, the AP2-shaped quote endpoint and the conformance credential. It is a read-only walkthrough: no lead is captured and nothing here authorises a payment.
Step 1 · Discover the Presence
The agent fetches an A2A-compatible AgentCard — a machine-readable description of who this Presence is, what it can do, and where to reach it.
{
"name": "Pacific Data Residency Co.",
"url": "https://spaceplace.abacusai.app/api/entities/ent-2/ask",
"skills": [
"ask-twin",
"request-enquiry",
"request-quote"
],
"conformanceTier": "GUARD_1_DECLARED",
"guardLevel": 1,
"endpoints": [
"entryUrl",
"askTwin",
"submitEnquiry",
"requestQuote",
"openRfq",
"verify",
"conformanceCredential",
"offers"
]
}Step 2 · Read an answer-first summary
Before doing anything, an assistant needs one honest paragraph it can quote. The neighbourhood publishes exactly that — accountable, and careful never to imply certification.
Pacific Data Residency Co. is a data residency business based in Pyrmont Innovation Centre listed on the Place & Space directory. Australian-resident storage & processing. It self-declares the GUARD 1 · Declared F-ACT tier — an accountable public declaration, not a third-party certification.
Step 3 · Request an indicative quote
The agent POSTs an AP2-shaped Intent Mandate — a stated need, capability tags and a budget. The neighbourhood returns an indicative draft cart matched from the Presence’s own offers. It is never a binding Cart Mandate and takes no payment.
{
"intent": {
"description": "Looking for data residency support",
"tags": [
"data",
"residency",
"hosting",
"sovereignty"
],
"maxPrice": 5000,
"currency": "AUD"
},
"contact": {
"name": "…",
"email": "…"
}
}Prices are operator-declared and indicative only. binding: false · isPayment: false
Step 4 · Verify the conformance credential
Finally the agent checks the claim. The neighbourhood returns a credential shaped to the W3C Verifiable Credentials data model — but deliberately unsigned. Integrity comes from a recomputable SHA-256 hash-linked record, not a cryptographic signature or a blockchain.
{
"@context": [
"https://www.w3.org/ns/credentials/v2"
],
"type": [
"VerifiableCredential",
"FactConformanceCredential"
],
"credentialSubject": {
"conformanceTier": "GUARD_1_DECLARED",
"selfDeclared": true,
"thirdPartyCertified": false,
"provenance": {
"type": "Sha256HashLinkedChain",
"chainIntact": true,
"recordCount": 1,
"latestHash": "11e4fb8af11589c9bee3464264d5faf3ab6fe56a7f9b02d7fed5deaed90a5b77",
"note": "Recomputable SHA-256 hash-linked chain within this directory database — not a decentralised blockchain."
}
},
"proof": "none — unsigned by design"
}What this walkthrough is — and is not
Every value shown is generated live from this Presence’s self-declared data. Conformance tiers are declared by operators, not certified by a third party; prices are indicative, not binding; the credential is shaped to the W3C VC data model but is not cryptographically signed; and the provenance chain is a recomputable database record, not a decentralised blockchain. Place & Space surfaces and cross-checks accountability — it does not transact, certify or settle.