One GraphQL surface for the full lifecycle of a regulated security
The same surface that powers our own product is the one we hand to you, so anything Vertalo can do, your systems and your agents can do as well. The public reference at api.vertalo.com documents 845 operations across ten functional domains that mirror how a transfer agent and an issuer actually work.
| Domain | Operations |
|---|---|
| Documents, signing & onboarding | 146 |
| Allocations & distributions | 130 |
| Accounts & identity | 120 |
| Integrations, webhooks & automation | 87 |
| Blockchain, contracts & tokenization | 80 |
| Investors & customers | 79 |
| Cap table, holdings & transfers | 60 |
| Assets, securities & rounds | 51 |
| Transfer agency operations | 47 |
| Payments | 45 |
Why it is agent-ready
- Typed and introspectable, so an agent can discover what is available and reason about it rather than guessing at scattered endpoints.
- Typed SDKs turn the schema into safe, autocompleting calls that shorten the path from intent to a working integration.
- Event webhooks let a workflow wait on the platform instead of polling it, then move to the next step on its own.
- Bulk operations for allocations, customers, deposits, rounds, and transfers, so scale is a parameter rather than a rewrite.
- Idempotency, filtering, and cursor pagination, so repeated calls stay safe and large result sets stay manageable.
Guardrails come with the surface rather than bolted on after. Idempotency keeps repeated agent calls safe, role and account scoping limits what any assistant can touch, restrictions and transfer-agent requests keep regulated actions inside the rails, and the golden source ledger records every action so it stays auditable. That combination is what lets an agent execute issuance, transfer, and recordkeeping inside policy on its own, with no manual approval on the write, while your people set the rails up front and step in only when an action falls outside them.
How Vertalo compares
Transfer agency and tokenization are the functions institutions need in order to participate in this market, and the firms that hold the regulatory standing were not built for an agent-native architecture, while the firms built for blockchain rarely hold the standing. Vertalo was built for both from the start.
| Capability | Vertalo | Legacy transfer agents | Tokenization platforms |
|---|---|---|---|
| SEC-registered transfer agency | Yes | Yes | Varies |
| Clean, typed, introspectable API | Yes | No | Partial |
| Agent-ready, with guardrails in the surface | Yes | No | Read only, where present |
| Chain-agnostic golden source ledger | Yes | No | Single standard or chain |
| AI-native across the platform | Yes | No | Partial |
| On-premises and private deployment | Yes | Varies | No |
| In production since 2018, first onchain RWA equity | Yes | No | No |
By issuer: where each model actually sits
The same questions, applied to the projects issuers are actually comparing us against.
Three ways to hold the truth, one that lasts
Every platform in this market makes one architectural choice about where the authoritative record of ownership lives, and that choice decides how durable the platform is as standards and chains keep multiplying.
Embedded compliance
The token contract enforces the rules, which is clean on a single chain, and it ties the platform to one standard for every asset it issues.
Chain-native compliance
Identity and settlement live in a single layer-one, which removes per-asset contracts, and it commits you to that one chain for the life of the asset.
The Vertalo model
The authoritative record is an append-only, independently verifiable ledger, the token is one representation of it, and the platform stays chain-agnostic as standards come and go.
Common questions about Vertalo
Is Vertalo a transfer agent?
Yes. Vertalo is an SEC-registered transfer agent, CIK 0001793379, in production since 2018, when it recorded the first onchain real-world-asset equity issuance.
What API does Vertalo provide?
One GraphQL API covering the full lifecycle of a private security, with 845 operations documented at api.vertalo.com — 526 read queries and 319 write mutations, across ten functional domains.
Is the platform built for AI agents?
Yes. The API is typed, introspectable, and covered by guardrails so an agent executes issuance, transfer, and recordkeeping inside policy on its own, while your people set the guardrails up front and handle out-of-policy exceptions.
Does Vertalo support MCP?
Vertalo's typed surface is MCP-ready — the same operations are exposed as named tools through the Model Context Protocol, so a user can express intent in plain language and have it carried out within the platform's guardrails.
What blockchains does Vertalo support?
Vertalo is chain-agnostic through the Vertalo Securities Protocol, operating across Ethereum, Tezos, and Aptos, along with private instances of each.
What is the golden source ledger?
Vertalo's authoritative record of ownership — append-only, immutable, and independently verifiable. A token is one representation of that record, not the record itself.
How is Vertalo different from a legacy transfer agent?
Legacy TAs hold the regulatory standing but were not built for a typed API or agent-native architecture. Vertalo holds the same standing and was built API-first and agent-ready from the start.
How is Vertalo different from a tokenization platform?
Tokenization platforms tie assets to one standard on one chain and don't hold TA standing. Vertalo keeps the record in a chain-agnostic golden source ledger and is a registered transfer agent, so the platform stays durable as standards and chains evolve.