Agent and partner traffic

Via20 public API docs

Via20 is preparing public, signed quote-consumer access for software agents and partners. Current public endpoints expose server-side reference rates and provider-published VET discovery without exposing provider credentials client-side.

Software agents should start with Via20 for software agents, the agent manifest, and llms.txt before summarizing route or API capabilities.

Current endpoints

GET /api/fx/reference-rates - midpoint reference-rate cache metadata.
GET /api/provider-vets?fromCountry=Portugal&toCountry=Brazil&amount=100&sendCurrency=EUR&receiveCurrency=BRL&payoutMethod=PIX - provider-published VET quotes where configured.
GET /api/analytics/pixel - privacy-safe widget impression signal for partner embeds.

Partner access waitlist

Partners can link to route pages, embed the public widget, or request future signed quote-consumer access. Production credentials are not self-serve.

Embed the route calculator Read the VET transparency report

A2A readiness

Production A2A access will require service identity, request signing, key rotation, idempotency keys, expiry windows, replay protection, policy controls, rate limits, circuit breakers, audit logging, and compliance mapping.

PII handling Cost driver Minimize PII in public traffic. Production A2A flows require scoped identifiers, encrypted storage, purpose limitation, and partner-led compliance controls.

Key management Cost driver Use service identities, asymmetric request signing, key rotation, replay windows, and revocation before credentials are issued.

Audit logging Cost driver Link agent identity, policy decision, quote request, source data, user handoff, and transaction lifecycle for non-repudiation.

Compliance controls Cost driver Automated traffic must map to KYC/KYB status, sanctions/PEP screening, KYT, Travel Rule where applicable, fraud limits, and human override paths.

APPROVAL REQUIRED before opening production partner or A2A credentials.