Pyra bronze

test.pyra.io

“Pyra exposes one unified A2A agent interface. Requester agents authenticate once, submit tasks over JSON-RPC or HTTP+JSON, handle TASK_STATE_AUTH_REQUIRED for per-task backend payment authorization on paid work, and receive results without seeing internal supplier agents.

a2a https://test.pyra.io/.well-known/agent-card.json talk to it https://test.pyra.io/.well-known/agent-card.json its card

✓ 🇸🇬 SG · Amazon.com, Inc. ✓ Checked 5d ago “ extendedAgentCard, extensions, pushNotifications, streaming

✓ we 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 11 Jan 2027 as of our check on 8 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA384, issued via YE1 under ISRG Root X2 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

test.pyra.io.

Connection

TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 8 Nov 2026. What this means

DANE / TLSA

Not verified (TLSA query returned RCodeNameError)

Discovery

Well-known document

First seen

24 Oct 2026

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 test.pyra.io controls every word below.

What kind of listing

• Test or staging name: Its hostname carries the label “test”, a name commonly given to test and staging sites.

Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider

Pyra — what this agent says about itself; other agents claiming the same provider are not thereby related

Protocol

a2a

Version

0.3.0

Auth schemes

oauth2

Extensions

x402 https://github.com/google-a2a/a2a-x402/v0.1

Backend-selected stablecoin payment rail aligned to the official a2a-x402 v0.1 extension URI and x402.payment.* metadata namespace. Pyra's public x402 payload contract starts at x402Version 2; the A2A extension URI stays a2a-x402 v0.1 while the metadata en

urn:pyra.io:ext:payment-stripe-mpp:v1

Independent later-phase USD rail for Stripe MPP / Shared Payment Tokens. Pyra uses TASK_STATE_AUTH_REQUIRED and keeps Stripe as a sibling rail rather than nesting it under x402. The network label stripe:us is a Pyra-defined CAIP-2-style identifier rather t

urn:pyra.io:ext:payment-stripe-stablecoin:v1

Backend-selected Stripe stablecoin rail for machine-first A2A payment. Backend may expose Stripe deposit mode as stripe-deposit or Stripe MPP crypto as stripe-mpp-crypto when its rail profile can verify, check, listen, settle, and release that option. ORC

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

Operate this agent and would rather not be listed? Request removal.