Paybond Protocol Trust Delegation bronze
api.paybond.ai
“A2A-aligned discovery surface for multi-party protocol-trust delegation into Paybond-managed Harbor flows.
https://api.paybond.ai/.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 20 Jan 2027 as of our check on 14 Nov 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.Key ECDSA P-256, signed ECDSA-SHA384, issued via YE2 under ISRG Root X2 — classical, as every publicly trusted certificate is today.
Names on this certificate (2)
*.paybond.ai,paybond.ai. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 14 Nov 2026. What this means
- DANE / TLSA
- Not verified
- Discovery
- Well-known document
- First seen
- 14 Nov 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
- 45m 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 api.paybond.ai controls every word below.
Create delegated commercial intent
Verify a portable mandate and replay-safe recognition proof before creating a Harbor intent for a multi-party delegated workflow.
- Create a Harbor intent for a marketplace booking agent acting under a tenant-approved mandate.
Submit delegated workflow evidence
Attach counterparty or performer evidence to a Harbor intent after agent recognition succeeds.
- Submit fulfillment evidence from a specialist agent after a delegated travel booking completes.
Confirm delegated settlement outcome
Finalize release or refund decisions in Harbor after the delegated workflow reaches a terminal outcome.
- Confirm release after predicate evaluation passes and the recognized operator approves settlement.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Paybond — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 2.0.0-preview
- Auth schemes
- paybondBearer
- Extensions
-
https://paybond.ai/extensions/a2a/task-contracts/v1— required of clientsPaybond task contracts that bind A2A discovery to protocol v2 mandate, recognition, and Harbor-managed workflows.A2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so. - Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extensions
- Agent card
- https://api.paybond.ai/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.