Eroya API and Payments Agent bronze

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 Google Trust Services domain-validated

Valid until 31 Jan 2027 as of our check on 9 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-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (3)

eroya.co, immi.eroya.co, *.immi.eroya.co.

Connection

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

DANE / TLSA

Not verified

Discovery

Well-known document

AI use policy

Search: yesAI input: yesAI training: no

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.

AI-facing documents

Publishes /llms.txt — “Eroya — U.S. & China Market Data” a curated map of the site's content for language models

Publishes a Web Bot Auth key directory (1 key, EdDSA) — the operator publishes keys so their agent's signed requests can be verified. agenttru.st recorded that the directory exists; it has not verified a signature.

Fetched from this host during verification. Neither document is how this agent was discovered.

First seen

9 Nov 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 www.eroya.co controls every word below.

Technical agent card

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

Provider

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

Protocol

a2a

Version

1.1.0

Extensions

AP2 https://github.com/google-agentic-commerce/ap2/tree/v0.1 — required of clients

Merchant for one-time USD plan access. Requires user-confirmed AP2 v0.1 mandates using the Eroya account-key ES256 profile and a Stripe Shared Payment Token. See https://eroya.co/ap2.md for key enrollment, cart review, signature verification and supported

AP2 https://github.com/google-agentic-commerce/AP2/tree/v0.1.0 — required of clients

Merchant for one-time USD plan access. Requires user-confirmed AP2 v0.1 mandates using the Eroya account-key ES256 profile and a Stripe Shared Payment Token. See https://eroya.co/ap2.md for key enrollment, cart review, signature verification and supported

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.