> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reinx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Give your AI agent a funded wallet with spending controls in minutes

<Steps>
  <Step title="Create your account">
    Sign up at [app.reinx.ai](https://app.reinx.ai) and create your organization. You can explore the dashboard and configure projects, teams, and policies right away — financial operations unlock once identity verification (KYC) completes.
  </Step>

  <Step title="Fund your treasury">
    Add funds from **Funding** in the dashboard. Bank transfers (ACH/wire) are free; balances are held as USD-pegged stablecoins and displayed in dollars.
  </Step>

  <Step title="Create an agent">
    From the dashboard, create an agent: give it a name, pick a team, set its **budget** and **approval threshold**. The agent gets its own non-custodial crypto wallet automatically.

    When it's created, copy the agent's **API key** — it starts with `sk_reinx_live_` and is shown **once**. This is the only credential your agent needs; it never touches wallet keys.
  </Step>

  <Step title="Connect your agent via MCP">
    Add the Reinx MCP server to your agent's configuration:

    ```json theme={null}
    {
      "mcpServers": {
        "reinx": {
          "type": "http",
          "url": "https://mcp.reinx.ai/mcp",
          "headers": {
            "Authorization": "Bearer sk_reinx_live_your_key_here"
          }
        }
      }
    }
    ```

    Or with Claude Code:

    ```bash theme={null}
    claude mcp add --transport http reinx https://mcp.reinx.ai/mcp \
      --header "Authorization: Bearer sk_reinx_live_your_key_here"
    ```
  </Step>

  <Step title="Make the first payment">
    Your agent can now check its remaining budget and pay for things — within the rules you set:

    ```json theme={null}
    // get_budget_utilization — remaining budget (the number that gates payments)
    { "purpose": "Verify available budget before subscribing to data feed" }

    // request_wallet_payment
    {
      "purpose": "Pay for the market data API subscription",
      "amountCents": 4900,
      "recipient": "0x7a3f...8c21",
      "caip2": "eip155:8453",
      "idempotencyKey": "datafeed-2026-07"
    }
    ```

    Payments at or below your approval threshold auto-approve and execute — unless another policy stage intervenes (an anomaly flag or a project/team approval rule can still route them to review, and hard limits can deny them). Anything above the threshold lands in your **Approvals** queue — approve or deny from the dashboard (you'll also be notified by email).
  </Step>
</Steps>

<Note>
  TypeScript and Python SDKs are coming soon. Today, agents connect through the [MCP
  server](/mcp-tools/overview) and humans/automations use the [REST
  API](/api-reference/authentication).
</Note>

## What's next

* [Payment Workflow](/mcp-tools/payment-workflow) — the request → poll → learn loop your agent should implement
* [Spending Policies](/concepts/spending-policies) — every control you can set
* [Approvals](/concepts/approvals) — how the human-in-the-loop works