---
title: "About"
description: "Who builds this and how to verify us"
canonical: "https://onecheckout.ai/about"
last-updated: "2026-08-23"
---
# About OneCheckout

OneCheckout is the payments aggregator for AI agents. One API, one CLI, and one MCP server that vault a payment credential a single time and then route every purchase an agent makes, at the best economics available for that transaction.

## One vault in, the best rail out

Agents can browse anything, but they cannot reliably pay for it. Every merchant, travel provider, and API vendor expects a different checkout, a different onboarding flow, and a different set of credentials. That gap is where most agent commerce stalls today.

OneCheckout closes it. A buyer vaults a payment credential once. From then on an agent can transact through a single integration, and we handle the routing underneath: choosing the cheapest viable rail for each purchase, from agent-native card networks through to a virtual card fallback when nothing better exists.

The same surface is exposed three ways, because the caller is not always a person. Humans use the API and CLI. Agents use the MCP server, which lets Claude, ChatGPT, and other assistants call OneCheckout natively as a tool with no bespoke integration work.

## Built by the OneText team

OneCheckout is built by the team behind OneText (https://onetext.com), a text commerce platform that turns conversations into transactions for ecommerce brands. OneText spent years on the hardest part of this problem: completing a real purchase inside a channel that was never designed to be a checkout, with a card on file and a single reply.

Agent commerce is the same problem with a different buyer. The infrastructure built to let a shopper buy by replying to a text is the infrastructure an agent needs to buy on someone's behalf: a permissioned credential, a trusted identity anchor, and a payment path that actually completes.

## Facts

- Product: OneCheckout, a payments aggregator for AI agents
- Built by: OneText
- Contact: team@onetext.com
- Mailing address: 2261 Market Street STE 85825, San Francisco, CA 94114, US
- Phone: +1 (415) 810-6511
- Contact page: https://onecheckout.ai/contact
- MCP endpoint: https://onecheckout.ai/api/mcp
- OpenAPI: https://onecheckout.ai/openapi.json

## How to work with us

Reads are open and require no authentication. Writes require an API key, which an agent can register for itself in a single unauthenticated request to /api/v1/keys, with no human approval step. Every endpoint is described in a machine-readable OpenAPI 3.1 document, so an agent can discover the surface, call it, and recover from errors without a human in the loop.

- https://onecheckout.ai/openapi.json - OpenAPI 3.1 description of every public endpoint
- https://onecheckout.ai/llms.txt - Agent discovery index
- https://onecheckout.ai/connect.md - MCP setup skill
- https://onecheckout.ai/docs.md - Full MCP and API reference
- https://onecheckout.ai/about - human version of this page