Toku
Toku is a Chile‑based fintech platform that provides B2B payment and collection solutions powered by intelligent AI agents. The platform automates invoicing, executes payments, reconciles transactions, and reduces delinquency, enabling businesses to increase cash flow and streamline financial operations. Backed by Gradient Ventures, Toku serves enterprises across Latin America.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Toku the way a machine reads it — 51 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Toku scores 51.3/100 (developing), with a separate agent-readiness read of 43/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-31 · rubric v0.25.0
Put this on your own site. The badge is drawn live from Toku's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/toku/"
title="Toku on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/toku.svg"
alt="Toku Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/toku/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/toku/"
title="Toku on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/toku/card.svg"
alt="Toku Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Toku
Each block below is one kind of artifact we hold for Toku. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 37
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Toku Adjustment Documents API
El objeto `Adjustment Document` es una nota de crédito o factura de proveedor que la organización puede aplicar como saldo a favor al momento del cobro. Si está ligado a una Inv...
Toku Auth API
Emisión y validación de tokens de acceso, resolución de API keys, verificación de reCAPTCHA y políticas de acceso por Organization.
Toku Beneficiaries API
Alta y mantención de los Beneficiaries: las personas o empresas que reciben un pago. Un Beneficiary agrupa los datos de identidad y una o más Beneficiary Accounts.
Toku Beneficiary Accounts API
Consulta y mantención de las Beneficiary Accounts: las cuentas bancarias asociadas a un Beneficiary, junto con su verificación bancaria y su flujo de aprobación.
Toku Boleto API
Emissão de boleto bancário no Brasil e acompanhamento do seu ciclo de vida: registro no banco, consulta do PDF, baixa quando o pagamento é confirmado e cancelamento. Nesta seção...
Toku Checkout Session API
Ciclo de vida de una Checkout Session: creación, consulta, actualización de su vencimiento y expiración. Incluye las operaciones que consume el portal de pago de Toku y las que ...
Toku Consulta de consentimientos API
API server-to-server con la que la organización consulta qué consintió una persona, para decidir qué pedirle antes de anunciar. Se autentica igual que los intents: la llama su b...
Toku Customer Collection Accounts API
Cuentas bancarias que un Customer deja registradas para que se le cobre por PAC o domiciliación bancaria.
Toku Customer Portal API
Endpoints que sostienen el Customer Portal de Toku: el portal web donde un Customer revisa sus Invoices y Subscriptions, inscribe medios de pago y paga. La mayoría de estas oper...
Toku Customers API
Consulta de la información de un Customer asociada a sus medios de pago, y asociación de un Payment Method con una Subscription.
Toku Débito Automático API
Cobrança de Subscriptions por Débito Automático no Brasil: cadastro das contas bancárias que o pagador autorizou no banco, geração dos arquivos de remessa enviados ao banco e pr...
Toku Debt Reconciliation Public API
The Debt Reconciliation Public API from Toku — 1 operation(s) for debt reconciliation public.
Toku Efectivo API
The Efectivo API from Toku — 2 operation(s) for efectivo.
Toku Electronic Signature API
Creación de Documents para firma electrónica, consulta de su estado y descarga del documento firmado.
Toku Facturación API
Facturación electrónica en México. Cubre las dos mitades del flujo: los datos de facturación que se guardan sobre un Customer o un Invoice, y la emisión de los billing documents...
Toku Forum API
Integración con Forum: configuración de la ventana de envío de cada organización, despacho de los Webhooks que informan los pagos y generación de los reportes diarios que los re...
Toku Intents de consentimiento API
API server-to-server con la que la organización anuncia cada consentimiento que va a pedir, antes de renderizar su formulario. La llama su backend con la api-key de Toku, y el g...
Toku Invoices API
Una `Invoice` contiene la información de una deuda. Para crearla se necesita el identificador público del `Customer` al que pertenece, que se obtiene al crearlo en Toku y tiene ...
Toku Llaves de encriptación API
Generación de las llaves con las que encriptas los datos de tarjeta antes de enviarlos. Toku soporta RSA 2048 con PKCS1_OAEP y AES 256 en modo CBC.
Toku PAC API
Medios de pago con cargo automático a una cuenta bancaria en Chile: PAC y los catálogos bancarios asociados.
Toku Payment Methods API
Administración de los Payment Methods de una Account: creación, consulta, edición, eliminación y carga masiva, además de la invalidación de los medios de pago que dejaron de est...
Toku Payout API
Consulta y gestión de Payouts: listado, detalle, aprobación, rechazo, edición de monto, comprobantes, actualización de estado y etapas de creación y ejecución en lote.
Toku Payout Request Ingestion API
Ingesta de Account Payables para crear un Payout Request —enviándolas por API o depositando archivos CSV en el SFTP de la organización— y avance de las filas resultantes hacia e...
Toku Payout Request Items API
Seguimiento y cierre de los Payout Request Items, las filas individuales que quedaron registradas al ingestar un Payout Request.
Toku Pix API
Operações de cobrança Pix integradas diretamente com os PSPs brasileiros: criação da cobrança, cadastro da chave Pix, cancelamento e recebimento das notificações de pagamento en...
Toku Pix Automático API
Cobrança recorrente por Pix Automático no Brasil: cadastro da recorrência no banco do pagador, cobrança das Invoices de cada ciclo, retentativas e cancelamento. Nesta seção, as ...
Toku POS Terminals API
Registro y administración de los terminales POS de la cuenta. Un terminal es el dispositivo físico donde se cobra, y queda asociado al adquirente con el que se registró: ese adq...
Toku Receipts API
Comprobantes de una operación y documentos tributarios asociados. Agrupa la generación del comprobante, su descarga mediante URL firmada, la configuración con que se despliega y...
Toku Refunds API
Devoluciones de dinero sobre un pago ya realizado. Toku registra cada devolución como una Transaction propia de tipo `REVERSED`, ligada al pago original, y la aplica sobre las I...
Toku Reports API
Motor de reportes por entidad: consulta de columnas y hojas disponibles, generación del reporte completo y procesamiento por partes de los reportes grandes.
Toku Risk flow validator executions API
Execution of risk validators: starting one, the state it is in, and the progress of its steps.
Toku Subscriptions API
El objeto `Subscription` define el cobro recurrente de un `Customer`.
Toku Tarjetas API
Endpoints que reciben datos de tarjeta, ya sea para cobrar una vez, para inscribir la tarjeta como medio de pago recurrente o para guardarla como PaymentInstrument sin cobrarla....
Toku Transactions API
Cobro y registro de Transactions sobre Invoices. Una Transaction agrupa el monto cobrado, el medio de pago usado y los Invoices que salda, e incluye tanto los cobros que procesa...
Toku Transferencias 🇨🇱 API
Bancos con los que un pagador puede pagar por transferencia en Chile, y con qué producto se paga en cada uno.
Toku Validación de Cuenta Clabe API
Verificación de titularidad de cuentas bancarias mexicanas (CLABE). Se confirma que una cuenta existe y que pertenece a la persona declarada realizando una micro transferencia p...
Toku Webhook Endpoints API
El objeto `Webhook Endpoint` registra una url y los eventos que deben ser notificados a traves de esta, para un cliente especifico.
Scroll within the panel for all 37 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Agent Skills 1
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
create-card-transaction
AGENT SKILLSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Toku Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Toku API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CheckoutSessionRequestV2Decryption
JSON SCHEMACreatedCheckoutSessionResponse
JSON SCHEMAPublicCheckoutSessionResponse
JSON SCHEMAUpdateWebhookEndpointPayload
JSON SCHEMAWebhookEndpointPayload
JSON SCHEMAWebhookEndpoint
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Toku — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/toku · machine-readable index on apis.io
This is an independent, third-party profile of Toku, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.