Blnk Finance
AgentCard object — a capabilities object, a declared protocolVersion, and a well-formed skills array.
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://docs.blnkfinance.com/
· transport HTTP+JSON
non-standard supportedInterfaces
blnk-core core
Prepare an application codebase to talk to Blnk Core (latest Core + SDKs, client, env, auth, secrets). Use when wiring Blnk into an existing app, upgrading Blnk versions, adding Blnk config or API keys, enabling secure mode expectations, or checking production readiness. Do not use this skill to implement the install quickstart or a first ledger/transfer demo.
blnk-documentation documentation
Record Blnk product decisions as numbered markdown files in .blnk_context/. Use when capturing money movement maps, ledger architecture, metadata structure, naming, precision, queueing, or any other Blnk design decision for the team; when starting or updating a Blnk integration context pack.
blnk-fx fx
Design and record Blnk currency exchange with nostro legs, FX spread, and multi-leg or multi-day settlement. Use when converting currencies, building FX or swaps, recording exchange rates or spread, implementing crypto order exchange, or modeling delayed settlement with intermediary balances.
blnk-implementation implementation
Turn a product or POC spec into a money movement map plus runnable Blnk app code, tests, and a verified run. Use when the user drops a spec, PRD, or POC doc and wants end-to-end implementation without writing the code themselves.
blnk-inflight inflight
Mental model and workflows for Blnk inflight transactions when other work must finish before a movement is complete. Use when authorizing then capturing, escrow holds, commit or void inflight, inflight expiry, split inflight, or bulk commit/void.
blnk-ledger-architecture ledger-architecture
Investigate product intent and design Blnk money movement maps (including maps-tool JSON) and ledger architecture before coding balances and transactions. Use when structuring ledgers, discovering reporting needs or connected tools, drawing fund flows, exporting map.blnkfinance.com JSON, grouping balances into ledgers, or planning General Ledger @ balances.
blnk-naming-patterns naming-patterns
Consistent names for Blnk ledgers, @ internal balances, transaction references, and meta_data keys. Use when naming indicators, General Ledger balances, references, ledger titles, or metadata join keys.
blnk-precision precision
Encode and display Blnk amounts correctly with precise_amount and a single precision source of truth (prefer currency enums). Use when handling cents, zero-decimal currencies, available balance display, converting human amounts, or preventing precision drift across services.
blnk-queueing queueing
Choose Blnk queue vs skip_queue per step from whether the next action needs an immediate ledger outcome or can proceed async. Use when setting skip_queue, mixing sync auth with async settlement, handling QUEUED status, or wiring confirmation after create or commit.
blnk-sdks sdks
Use official Blnk SDKs (TypeScript, Go, Python, and Java) with shared client behavior; fall back to HTTP only when no Blnk SDK covers the language or endpoint. Use when initializing Blnk clients, calling ledger APIs from apps, or choosing between SDK and raw HTTP.
blnk-support support
Escalate uncertain or high-stakes Blnk design and production questions to the Blnk Support team instead of inventing a solution. Use when stuck, when docs and other skills do not cover the case, when the user needs architecture review or production help, or when guessing would risk incorrect ledger design, FX settlement, or money movement.
blnk-transactions transactions
Post and manage applied Blnk transactions—overdraft policy, bulk vs multi-source/destination, scheduling vs cron, backdating, refunds, and lifecycle. Use when creating or updating applied transfers. For holds load blnk-inflight; for skip_queue load blnk-queueing; for amounts load blnk-precision; for cross-currency load blnk-fx; for contention load blnk-queueing hot-balances.
blnk-watch watch
Design Blnk Watch risk controls—clean .ws rules, a risk-score rubric, and Watch configuration—via a question-driven workflow. Prefer Blnk Cloud with embedded Watch over self-hosting the Watch binary. Use when writing or reviewing watch scripts, assigning scores or verdicts, consolidating risk outcomes, configuring Cloud Watch / WATCH_SCRIPT_* / ALERT_WEBHOOK_*, or wiring Watch next to Core.
blnk-webhooks webhooks
Subscribe to Blnk webhooks and transaction hooks securely with HMAC verification and idempotent handlers. Use when handling X-Blnk-Signature, transaction.applied events, PRE/POST hooks, or keeping app state in sync after money movements on either the queued or skip_queue path.
2026-08-27 from https://docs.blnkfinance.com/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.