# Talo Partner Hub for agents > Start here: what the hub does, how to connect, and where every page is. Bank-transfer payments in Argentina on a Talo Pay account: each payment gets its own CVU and alias, the buyer transfers ARS from any bank, and the hub tells you when it lands. Everything works the same in **sandbox** (test money, simulated transfers) and **production** (real money). ## The fastest path 1. Connect the MCP server: `https://talopartnerhub.vercel.app/api/mcp`. Clients with OAuth (Claude Code, Claude Desktop, Cursor) open the browser for the person to authorize; no key is pasted anywhere. See [mcp](https://talopartnerhub.vercel.app/docs/mcp.md). 2. Test the whole flow in sandbox yourself: create_payment → simulate_transfer → get_payment / list_events. See [sandbox](https://talopartnerhub.vercel.app/docs/sandbox.md). 3. Integrate in code with the REST API and signed webhooks. See [api](https://talopartnerhub.vercel.app/docs/api.md) and [webhooks](https://talopartnerhub.vercel.app/docs/webhooks.md). 4. Run check_go_live (or GET /api/v1/readiness) until it says ready, then repeat in production. See [go-live](https://talopartnerhub.vercel.app/docs/go-live.md). A person has to authorize the Talo account once per environment (Talo requires it). After that, you can do everything else: create payments, simulate transfers, register and ping webhooks, create narrower keys, check readiness. No checkout to build? A reusable payment link (`/l/`, with a QR) sells with no code, and the `` widget shows a payment on the merchant's own page with one script tag. See [checkout](https://talopartnerhub.vercel.app/docs/checkout.md). `npx talo-hub login` waits until the person authorizes and then exits by itself (0 = connected): that exit is your signal, so don't ask them whether they authorized. Show them the link and code it prints; they compare the code in their browser. If your tool notifies you when a background command exits (Claude Code's background commands do), run it in the background and continue when that notice arrives; otherwise run it in the foreground with a timeout of at least 10 minutes. If it gets cut off, run the same command again: it picks up the same login, with the same link and code. If it expired, running it again checks once whether the person finished in Talo anyway (and collects the key), and otherwise starts a new login with a new link and code. The hub is run by an official partner of Talo Pay and the money stays in the merchant's Talo account; [security](https://talopartnerhub.vercel.app/docs/security.md) says who operates it, what it stores and how the person revokes keys or disconnects the account. ## Pages - [Quickstart](https://talopartnerhub.vercel.app/docs/quickstart.md): From nothing to a paid sandbox payment in five commands. - [Sandbox: test everything yourself](https://talopartnerhub.vercel.app/docs/sandbox.md): Simulated transfers, every payment status, webhook pings, and the end-to-end test plan. - [Credentials: sandbox and production, safely](https://talopartnerhub.vercel.app/docs/credentials.md): Key types and scopes, where to keep them, least privilege, rotation, and what never to do. - [Security: what the hub stores and how to revoke it](https://talopartnerhub.vercel.app/docs/security.md): Who operates the hub, what it keeps (secrets encrypted), what each key can do, and how to revoke one key or disconnect the whole account. - [From sandbox to production](https://talopartnerhub.vercel.app/docs/go-live.md): The readiness checklist and the exact steps to start charging real money. - [MCP server](https://talopartnerhub.vercel.app/docs/mcp.md): Connect with OAuth or a key, and every tool with its scope. - [CLI](https://talopartnerhub.vercel.app/docs/cli.md): talo-hub commands, environments and non-interactive use. - [REST API](https://talopartnerhub.vercel.app/docs/api.md): Every endpoint with its fields, the payment object, errors and payment statuses. - [Webhooks](https://talopartnerhub.vercel.app/docs/webhooks.md): Events, the exact signature format, verification code, retries, ordering and a test vector. - [Checkout: payment links and the transfer widget](https://talopartnerhub.vercel.app/docs/checkout.md): Talo's payment page, reusable payment links (/l/, with a QR) and the widget or shadcn component, with the read-only checkout_token behind it. - [Integrate on any stack](https://talopartnerhub.vercel.app/docs/stacks.md): One kit of best practices per stack (Next.js + Vercel, Node, Python, Laravel, edge), the contract every integration meets, and how to port it to any other stack. - [Skills](https://talopartnerhub.vercel.app/docs/skills.md): SKILL.md files that teach an agent to integrate and operate Talo. Also: [llms.txt](https://talopartnerhub.vercel.app/llms.txt), [llms-full.txt](https://talopartnerhub.vercel.app/llms-full.txt), [OpenAPI](https://talopartnerhub.vercel.app/openapi.json), [MCP server card](https://talopartnerhub.vercel.app/.well-known/mcp.json). Every human page under https://talopartnerhub.vercel.app/docs also answers `Accept: text/markdown` with its Markdown. --- Human page: https://talopartnerhub.vercel.app/docs/agents · All pages: https://talopartnerhub.vercel.app/docs/index.md