> ## 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.

# Changelog

> User-visible changes to Anchorage Agentic Banking and these docs.

<Update label="2026-07-08" description="These docs have a new home">
  This documentation now lives at docs.anchorage.com/agentic-banking. Old
  links under agentic.anchorage.com/docs redirect here automatically, so
  bookmarked pages keep working. The docs MCP server moved with it: requests
  to the old address are redirected with the method preserved, which most
  MCP clients follow transparently — if yours does not, update its
  configured address to docs.anchorage.com/mcp. Updating saved links is a
  good idea either way.
</Update>

<Update label="2026-06-26" description="One merchant catalog, richer results, for agents and browsers">
  Finding a merchant now happens in one place: the merchant catalog, browsable
  by anyone in the web UI — signed in or anonymous — and searchable by agents
  over MCP. An agent's results are limited to what it can actually pay on its
  network (mainnet or testnet), and this catalog search is now the only way
  an agent discovers where it can pay; the earlier separate list of allowed
  merchants has been retired in its favor. Each result now also shows
  the merchant a service belongs to, whether that merchant runs the service
  itself or resells another provider's, and the payment methods the service
  accepts, so an agent can tell up front what it's able to pay and who it's
  dealing with. Services from the same merchant are grouped together, and
  pulling a single service's detail lists the payment methods its endpoints
  accept. Only merchants that have cleared review appear in results.
</Update>

<Update label="2026-06-26" description="Agents can report catalog gaps and broken services">
  Agents can now report problems with the merchant catalog as they browse it. When
  an agent cannot find a merchant it expected, finds that no merchant offers what
  it needs, hits a service that does not work, or gets search results that miss the
  mark, it can send that feedback to Anchorage Agentic Banking — noting the search
  it tried or the service in question. The reports help us fill gaps in the catalog
  and fix listings that have gone stale.
</Update>

<Update label="2026-06-23" description="Solana deposit setup warning">
  The Deposit page now warns when a Solana deposit address still needs its token
  account created. If you see the warning, complete the setup before sending
  funds to that Solana address. Existing ready addresses are unchanged.
</Update>

<Update label="2026-06-22" description="Pay and fund with USDC on Solana">
  Agents can now make crypto payments with USDC on Solana, alongside USDC on
  Base — Anchorage Agentic Banking automatically settles on Solana when a
  merchant prices a request there. You can also fund your account by depositing
  USDC on Solana; it credits your account's USD balance on that network
  (mainnet or testnet — Base and Solana deposits feed the same balance, not
  separate ones per chain) and is screened like any other deposit. Existing
  Base payments and deposits are unchanged.
</Update>

<Update label="2026-06-22" description="Repeat deposits can reuse sender details">
  After you attribute a self-hosted deposit sender once, later deposits from the
  same sender in your org can reuse those details automatically. The deposit still
  runs screening before funds become available, so a fresh review can still block
  the funds.
</Update>

<Update label="2026-06-20" description="Agents can search the merchant catalog">
  Agents can now find merchants and services to pay by describing what they
  need — for example, "weather data" or "image generation" — instead of needing
  a URL up front. Search returns the matching live merchants, and an agent can
  then pull a service's payable endpoints and documentation links to make the
  call. Only merchants that have cleared review appear in results.
</Update>

<Update label="2026-06-17" description="Stronger linked-card compliance screening">
  Linked-card compliance screening was strengthened. As before, a card that does
  not pass is refused at link time and stays in your card list, marked with the
  reason.
</Update>

<Update label="2026-06-15" description="Attribute a held deposit">
  When a deposit reads **Needs attribution**, you can now enter the sender's
  name and country directly from your deposit history. Submitting those details
  runs the review and releases the funds in the same step if it passes.
</Update>

<Update label="2026-06-14" description="Blocked agent connections end the session">
  When an agent connection does not pass compliance screening, its session now
  ends, not just the one request it was making. The agent must reconnect to
  continue. No action required — a runaway agent is stopped at the connection,
  not asked again on the next call.
</Update>

<Update label="2026-06-14" description="Deposit screening labels">
  Each deposit now shows where it stands in review: **Needs attribution**,
  **Reviewing attribution**, **Cleared**, or **Blocked on screening**. A deposit
  becomes available to spend once it reads **Cleared**. The label sits next to
  each deposit in your deposit history, so you can tell at a glance whether
  funds are ready or still in review.
</Update>

<Update label="2026-06-10" description="Larger paid-URL responses">
  Paid URLs that return large payloads now come back to your agent whole.
  Responses up to 10 MB are delivered in full instead of being cut short, so
  data-heavy APIs behind a paid URL work as expected.
</Update>

<Update label="2026-05-28" description="Linked-card compliance screening">
  Linked-card support now runs compliance screening when a card is linked and on
  each purchase. A card or purchase that does not pass is refused; rejected cards
  stay visible in your card list for audit, marked with the reason. No action
  required — if a link or purchase is refused, the web UI explains why.
</Update>

<Update label="2026-05-27" description="Pilot launch and public docs">
  The first public release of **Anchorage Agentic Banking**, alongside the
  launch of this docs site.

  * **Two payment rails.** Crypto payments to paid URLs on the open
    internet, and linked-card purchases via a one-shot credential scoped
    per merchant. Each agent can use both rails and picks one per spend.
  * **Agent-scoped budgets.** Org admins pre-authorize crypto spend with
    a USD spend limit and a merchant allowlist; agents see the limit, not
    the account balance.
  * **Per-purchase passkey approval for linked cards.** Each card purchase
    an agent requests goes through a fresh passkey approval in the
    browser.
  * **Safety cap that no approval can override.** \$1,000 per UTC day, per
    agent, across both rails.
  * **Instant revoke** of any agent from the web UI, with no grace window.
  * **Sign-in** via work SSO or a one-time email code.

  Orgs fund their account by stablecoin deposit on the supported crypto
  chains; each deposit credits the account as USD at confirmation. Bank
  linking and ACH deposits are on the roadmap.

  The docs cover the [agent connection flow](/agentic-banking/guides/connect-an-agent),
  the [concepts](/agentic-banking/concepts/agents) behind agents, accounts, budgets,
  payments, and linked cards, and per-action
  [how-to guides](/agentic-banking/guides/make-a-crypto-payment).
</Update>