KYA-BRASIL
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kya_verifyA | Free. Who answers for this AI agent? Looks up the agent's KYA Brasil credential at the issuer and returns the principal (a Brazilian company with CNPJ and name, or a person verified by e-CPF with nothing personal), the mandate, the live status (active, suspended, revoked, expired) and its history. Give credential_id, or the agent key to find its active credentials. Use it before trusting an order, payment or signature that comes from an agent. |
| kya_revocationsA | Free. Credentials the issuer revoked since a date (default: the last 30 days). For verifiers that cache credentials and want to drop revoked ones. |
| kya_sign_linkA | Free. The link to send to whoever holds the e-CNPJ or e-CPF (owner, accountant, the person) so they see what is being authorized and sign in the browser. Use after a registration: give credential_id and challenge_id, and the agent's signature of the challenge so the holder only signs with the certificate. |
| kya_check_actionA | $0.01 (x402, USDC on Base; set KYA_PRIVATE_KEY). May this agent perform this action under its mandate, and is its credential active right now? The issuer answers with a signed verdict that lists every rule it evaluated, usable as evidence in a dispute. For a free, unsigned answer use kya_check_mandate on the mandate from kya_verify. |
| kya_verify_paidA | $0.01 (x402, USDC on Base; set KYA_PRIVATE_KEY). Same answer as kya_verify, without the free daily limit, plus a signed receipt of the verification. |
| kya_check_mandateA | Free and offline. Evaluates an intended action against a KYA mandate (the credential's mandate from kya_verify, or one you are drafting) and lists every rule with its result: action, ceilings per operation and per day, currency, counterparty (with *.domain wildcards), payment instrument, validity window. Nothing is sent anywhere. |
| kya_validate_mandateA | Free and offline. Checks a mandate against the KYA schema before registering an agent with it, and returns it normalized (actions deduplicated, counterparties and payment instruments normalized). Refuses card numbers and malformed fields with the reason. |
| kya_verify_credential_offlineA | Free. Checks a credential document you already hold: the issuer's Ed25519 signature (key from the issuer's /.well-known/kya.json, fetched once) and the expiry. It cannot see a revocation made after issuance (live_status is unknown); use kya_verify for the live status. |
| kya_verify_delegationA | Free and offline. A sub-agent acts under a delegation chain signed by the credential's agent (KYA-Delegation header). Checks every link (signatures, depth, lifetime, each mandate contained in the one above) against the credential, returns the key that must sign the sub-agent's requests, and, when an action is given, evaluates it on every level: allowed only if all of them allow it. |
| kya_aboutA | Free and offline. What KYA Brasil is, how an agent gets a credential, which tools to use as a verifier, and where the specification and the issuer's keys are. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Several tool pairs overlap heavily (kya_verify vs kya_verify_paid, kya_check_action vs kya_check_mandate, kya_validate_mandate vs kya_check_mandate), but the descriptions explicitly cross-reference each other and state when to use the free/offline vs live/paid variant, so boundaries are largely recoverable. An agent must read carefully to pick the right variant, which keeps this from a 5.
All tools share a consistent kya_ snake_case prefix followed by a verb_noun form (validate_mandate, check_action, verify_delegation). Minor deviations exist: kya_revocations and kya_about are noun-only with no verb, and the verify family uses inconsistent suffixes (verify, verify_paid, verify_credential_offline).
Ten tools is well within the ideal 3-15 range and each covers a distinct verification/validation concern for the KYA credential lifecycle. No tool feels gratuitous given the breadth of the domain.
The surface covers the full verifier lifecycle: pre-registration mandate validation, signing link, offline and live credential verification, action/mandate checks, revocation polling, delegation chains, and documentation. Only minor gaps, such as issuance itself being external, keep it short of perfect coverage.