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

# Quickstart

> From zero to first agent payment.

<Steps>
  <Step title="Sign in">
    Go to [agentic.anchorage.com](https://agentic.anchorage.com), choose
    **Sign in**, and use your org's SSO or the account your admin set up for
    you. Your first sign-in lands you on the organization picker, which lists
    every organization you can enter: accept a pending invitation, or join an
    organization that is open to your email domain. Once you belong to one,
    signing in takes you straight there.

    An organization is open to your email domain when it admits anyone with an
    address at that domain. If one matches an address you have verified and
    you are not a member, it appears under **Organizations you can join**, with
    a Join button. You join at the standard member role, so accept an
    invitation instead when someone invited you as an admin. Look for it on the
    organization picker when you have no organization yet, and on **Settings**
    once you do — an organization that opens up after your first sign-in shows
    up there without your having to sign in again.

    An organization with mainnet access admits only members whose identity
    Anchorage has verified, so Anchorage sends its invitations with that
    identity attached. If accepting an invitation is refused because no
    verified identity is linked, ask your organization's admin to contact
    Anchorage. Your invitation stays open while they do. If joining an
    organization open to your email domain is refused for the same reason,
    ask its admin to have Anchorage invite you with your identity attached.

    An organization is ready to use from
    the moment Anchorage creates it, so there is no activation step between
    your invitation and your first sign-in. If an organization's setup did not
    finish, that invitation admits you once Anchorage completes the setup, or
    sooner if another of your invitations or memberships already points
    somewhere active; until then it waits on your pending invitations marked
    **Setup incomplete**.
  </Step>

  <Step title="Connect an MCP client">
    Point any MCP-capable agent at Anchorage Agentic Banking. The MCP endpoint
    and OAuth consent are linked from the **Agents** page in the web UI.

    See [Connect an agent](/agentic-banking/guides/connect-an-agent) for tested clients and
    per-client setup.
  </Step>

  <Step title="Let the agent introduce itself">
    Once connected, your agent introspects its own identity on its first turn:
    name, linked account, and the budgets it can spend against —
    everything it needs to start paying.
  </Step>

  <Step title="Spend">
    Ask the agent to fetch a paid URL. The agent pays the URL using its
    standing budget. Anchorage Agentic Banking checks the budget and the
    merchant allowlist, settles the payment, and returns the merchant's
    response to the agent — which returns it to you.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="How budgets work" href="/agentic-banking/concepts/budgets">
    How agents are pre-authorized to spend, and what the spend limit means.
  </Card>

  <Card title="Connect an agent" href="/agentic-banking/guides/connect-an-agent">
    Per-client setup walkthroughs.
  </Card>

  <Card title="Crypto payments" href="/agentic-banking/concepts/payments">
    The mechanics behind the crypto rail.
  </Card>

  <Card title="Agents" href="/agentic-banking/concepts/agents">
    How an agent is authorized, and how to revoke one instantly.
  </Card>
</CardGroup>


## Related topics

- [Quickstart](/knowledge-base/platform/developers/trading/quickstart.md)
- [Vaults quick-start](/knowledge-base/porto/getting-started/accounts-vaults.md)
- [Changelog](/agentic-banking/changelog.md)