MCP Server Overview

The Reinx MCP server connects AI agents to financial infrastructure. Works with Claude, ChatGPT, and any LLM that supports MCP.

Two tool bands, one URL

The server serves two disjoint tool bands, selected by the credential you connect with:

You connect with	You get	For
Agent key (`sk_reinx_live_…`)	This page — 13 spend tools	One agent spending under policy
Organization key (`reinx_org_live_…`)	Management band — 21 tools	An orchestrator managing a fleet of agents

The bands never overlap. An agent-key connection cannot see a management tool, and an organization-key connection cannot see a spend tool — the server registers one band per connection, so this is structural rather than a per-call permission check. An agent can therefore never create, reconfigure, or unpause itself.

Server URL

https://mcp.reinx.ai/mcp

Same URL for both bands.

Configuration

{
  "mcpServers": {
    "reinx": {
      "type": "http",
      "url": "https://mcp.reinx.ai/mcp",
      "headers": {
        "Authorization": "Bearer sk_reinx_live_your_key_here"
      }
    }
  }
}

Or with Claude Code:

claude mcp add --transport http reinx https://mcp.reinx.ai/mcp \
  --header "Authorization: Bearer sk_reinx_live_your_key_here"

Available tools — agent band

Tool	Description
`check_balance`	Live wallet holdings (per-asset + USD total). Use `get_budget_utilization` for remaining budget — under just-in-time funding the wallet balance can be low while budget is available
`request_wallet_payment`	Request a wallet payment on any supported network (Base, Polygon, Arbitrum, Optimism, Solana)
`get_transactions`	Agent’s own transaction history
`get_spending_rules`	Returns agent’s spending policy
`get_denial_feedback`	Recent denial reasons with human feedback
`get_agent_status`	Status, budget utilization, health indicator
`submit_approval_request`	Request human approval for a planned purchase
`get_budget_utilization`	Budget vs actual for a time period
`list_approved_merchants`	MCC allowlist or approved merchant list
`get_wallet_addresses`	EVM and/or Solana wallet addresses
`check_merchant_allowed`	Pre-check if a merchant is allowed
`get_spending_summary`	Spending breakdown by category, merchant, day
`check_approval_status`	Poll for approval result on a pending request

Card-rail tools (request_card_payment, request_spt) ship with the card launch, expanding this band to 15 tools. A 16th, request_budget_increase, is deferred separately. Neither affects the management band.

Requirements

Every tool call requires a valid API key.
Every tool call requires a purpose field (3–500 characters) explaining why the agent is acting — recorded for audit and scoring.
All calls are written to an immutable audit log.

Go deeper

Payment Workflow

The request → poll → learn loop, idempotency, and status semantics.

Tool Reference

Exact parameters and limits for every tool.

Management Band

The 21 tools an organization key sees — provisioning and reconfiguring agents.

Organization Keys

Scopes, container bindings, and quotas for machine principals.

Getting Started

Concepts

MCP Tools

Orchestrators

API Reference

Support

MCP Server Overview

Two tool bands, one URL

Server URL

Configuration

Available tools — agent band

Requirements

Go deeper

Payment Workflow

Tool Reference

Management Band

Organization Keys

​Two tool bands, one URL

​Server URL

​Configuration

​Available tools — agent band

​Requirements

​Go deeper

Payment Workflow

Tool Reference

Management Band

Organization Keys

Two tool bands, one URL

Server URL

Configuration

Available tools — agent band

Requirements

Go deeper