From your first agent to an agent workforce.
One agent or a fleet — same wallets, same rules, same visibility.
Developer
One API call creates an agent with a wallet, scoped credential, and server-enforced budget boundary.
Founder & SMB
Give each agent its own balance, budget, approval threshold, and visible transaction history.
Enterprise
Keep organization, project, and team boundaries visible as roles, policies, and audit history scale.
One API call. A scoped wallet. Rules outside the prompt.
Plain HTTP and MCP. The financial boundary stays portable across runtimes — no proprietary SDK, no lock-in.
Create the agent
One POST to /v1/agents with a name, team, and budget.
Store the key once
The scoped agent credential is returned once and stored in your secret manager.
Connect over MCP
Point any compatible runtime at the HTTP endpoint and get all 13 tools.
Let policy decide
Budget, velocity, and approval rules run outside the agent before payment executes.
curl -X POST https://api.reinx.ai/v1/agents \
-H "Authorization: Bearer $CLERK_SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "ad-spender",
"teamId": "00000000-0000-4000-8000-000000000000",
"budgetCents": 50000
}'Wallet infrastructure and a default policy are created with the agent.
{
"mcpServers": {
"reinx": {
"type": "http",
"url": "https://mcp.reinx.ai/mcp",
"headers": {
"Authorization": "Bearer ${REINX_AGENT_KEY}"
}
}
}
}Stop sharing one company payment method across every agent.
Separate balances, budgets, and histories per agent — so you always know who spent what, and why.
Separate every agent.
Give each agent its own balance, transaction history, budget, and scoped key.
Keep policy outside the prompt.
Deterministic budget and payment checks run before a wallet payment executes.
Review the exceptions.
See amount, purpose, agent, and expiry context before you approve or deny.
Pause without destroying access.
Block new payments for one agent while retaining its identity and credential.
More teams and agents. The same clear boundaries.
Organization, project, and team scope stays visible across access, policies, approvals, and audit history — one control plane, every department.
Access roles
Audit history
Current scopeOrganization ownership
Keep billing, KYC, funding, integrations, and top-level security organization-scoped.
Project and team boundaries
Group agents by operational scope while preserving inherited budgets and permissions.
Six role levels
Assign owner, admin, project, team, operator, and viewer access at the right scope.
Scoped audit history
Keep role, policy, approval, and agent lifecycle changes visible to authorized teams.
Found your workflow?
Give it a wallet.
Join the waitlist and be the first to deploy agents that handle real money.