banking77 Banking Agent bronze

banking-agent-dpu.g9482.eqtylab.io

“Classifies retail-banking customer messages into the 77 banking77 intents with a fine-tuned Nemotron Nano 4B. Never sees the gold labels.

a2a https://banking-agent-dpu.g9482.eqtylab.io/a2a talk to it https://banking-agent-dpu.g9482.eqtylab.io/.well-known/agent-card.json its card

🇨🇦 CA · Hypha Worker Co-operative Inc. Checked 6d ago pushNotifications, stateTransitionHistory, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

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

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

Key RSA 2048, signed SHA256-RSA, issued via YR2 under ISRG Root X1 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

banking-agent-dpu.g9482.eqtylab.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: 9 Oct 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: 🇨🇦 CA · Hypha Worker Co-operative Inc. (AS32001)
Last checked: 6d 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 banking-agent-dpu.g9482.eqtylab.io controls every word below.

classify

Send one customer message as a text part. The agent triages it first: one of the 500 held-out prompts goes to the model and the reply is its banking77 label; anything else is answered 'elevate to human' without a model call. Either way the reply carries the id of the signed record (chat-…), which the Evaluator verifies. Data: {label, raw, record_id, predictions_cid}.

classification

Examples it gives

I still have not received my new card

classify held-out batch

Text 'classify held-out' (all 500) or 'classify held-out N', or data {"skill": "classify-heldout", "limit": N}. From text the reply waits for the result; from data it returns a working task to poll with tasks/get. On completion: {run_id, limit, rows, predictions_cid}. Predictions and the signed work-log go to blob under run_id, for the Evaluator.

classificationbatch

Examples it gives

classify held-out
classify held-out 5

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.

Technical agent card

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

Protocol: a2a
Version: 0.1.0
Card completeness: a2a.proto v1.0 requires eight top-level fields. This card omits:
supportedInterfaces

Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.

View all card details

Capabilities: pushNotifications stateTransitionHistory streaming
Agent card: https://banking-agent-dpu.g9482.eqtylab.io/.well-known/agent-card.json

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