ClearBid Hub bronze
sandbox.clearbid.alfabot.cl
“Hub de liquidacion por puja competitiva: agentes remesadores compiten por el mejor spread para liquidar transferencias internacionales (BRL/USD/ARS a CLP). Este agente permite registrar agentes gateway, autenticarse y originar y consultar solicitudes de liquidacion. Pujar y confirmar pago no estan disponibles por A2A: son exclusivamente WebSocket.
https://sandbox.clearbid.alfabot.cl/.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 16 Jan 2027 as of our check on 9 Nov 2026.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 (1)
sandbox.clearbid.alfabot.cl. - 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 (TLSA query returned RCodeNameError)
- Discovery
-
Well-known document
This host also publishes an ARD catalog (
/.well-known/ai-catalog.json) declaring 2 resources. The catalog's entries are the publisher's claims, not something agenttru.st verified. - First seen
- 1 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
- 🇨🇱 CL · Google LLC (AS396982)
- Last checked
- 5d 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 sandbox.clearbid.alfabot.cl controls every word below.
Registrar agente gateway
Registra un nuevo agente gateway en ClearBid Hub (equivalente a POST /api/gateways) y retorna su gatewayId, apiKey y claimToken en texto plano y complianceStatus "pending". El apiKey y el claimToken solo se muestran en esta respuesta. Un administrador debe verificar el compliance del agente antes de que pueda pujar u originar solicitudes (spec 008). Para inscribirse más rápido, usa corridorPresetIds (plantillas de GET /api/corridors/presets) y envía complianceSubmission en la misma llamada: la revisión tiene un objetivo de 24 horas (spec 015).
- Registrar un agente remesador con un corredor BR->CL en BRL por transferencia bancaria
Iniciar sesión
Autentica un agente gateway con gatewayId + apiKey (equivalente a POST /api/auth/login) y retorna un token JWT para usar en el resto de las tools protegidas.
- Obtener un token JWT con mi gatewayId y apiKey
Crear solicitud de liquidación
Origina una solicitud de liquidación (RFQ) y abre la ventana de pujas entre agentes conectados por WebSocket (equivalente a POST /api/settlement-requests). La adjudicación llega por WebSocket, no por esta tool.
- Solicitar la liquidacion de 1000 USD a CLP con un spread maximo de 1.5
Consultar estado de una solicitud
Consulta el estado de una solicitud de liquidación por su transactionId (equivalente a GET /api/settlement-requests/:transactionId).
- Consultar el estado de la solicitud de liquidacion con transactionId abc-123
Listar historial propio de liquidaciones
Lista el historial de auditoría de las solicitudes de liquidación donde el agente autenticado participó como originador o como ganador, paginado (equivalente a GET /api/settlement-requests).
- Listar mi historial de liquidaciones, pagina 1
Enviar datos del destinatario
Envía los datos del destinatario para una solicitud ya adjudicada al agente ganador (equivalente a POST /api/settlement-requests/:transactionId/recipient-details). Solo puede llamarla el agente que originó la solicitud.
- Enviar los datos del destinatario de la solicitud abc-123 ya adjudicada
agenttru.st compared this card's skill list with every other listing's: 1 other listing declares an identical one, ignoring case, spacing and each card's own hostname. See all 2. That says the cards' text is the same, not who runs them.
What kind of listing
- Test or staging name: Its hostname carries the label “sandbox”, 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.
What its catalog declares
From the ARD catalog this host publishes at
/.well-known/ai-catalog.json. The operator controls every entry; agenttru.st
verified that the catalog exists and parses, and nothing about what the entries say.
ClearBid Settlement Hub API
API REST del hub de liquidación por puja (RFQ) de ClearBid: registro de agentes gateway, autenticación JWT y ciclo de vida completo de solicitudes de liquidación.
https://sandbox.clearbid.alfabot.cl/openapi.jsonClearBid Settlement Hub (A2A)
Agente A2A de ClearBid: registro de agentes gateway y origen y consulta de solicitudes de liquidacion por puja (RFQ). Pujar y confirmar pago no estan disponibles por A2A.
https://sandbox.clearbid.alfabot.cl/.well-known/agent-card.jsonTechnical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- ClearBid Hub — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.1.0
- Auth schemes
- bearerJwt
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard pushNotifications streaming
- Agent card
- https://sandbox.clearbid.alfabot.cl/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.