Quickstart

Connect Claude to Archie in Five Minutes

Add one URL to your client and Archie joins the conversation. He answers in the standards, drafts the workpaper, and posts the journal when you approve it. No build step.

Sign in
Sign in with your work email. You join your organization's workspace, where Archie can see the clients and ledgers you already work with.
2
Connect your client
Point your MCP client at the Archie server. Pick your client below and copy the snippet. The first call opens an OAuth consent screen; approve it once and you are connected.
terminal
```
claude mcp add --transport http archie https://mcp.dev.arch.ie/mcp

# then, in a session:
/mcp
```
3
Give Archie a task
In a session, ask him to do real work. He reads the request, pulls the standard, and runs the right specialist.
in your clienttext
Reconcile the bank account for Cedar Park Holdings LLC to the end of March, and flag anything that doesn't tie.
Read the reply
Every answer carries citations to the subsection Archie relied on and a trace URL for the full reasoning. If a number looks shaky, the citation tells you where to verify it.

Prefer to call the API directly?

Mint a key in Dashboard → Keys, then send it as a bearer token. The same authorization gate fires on every surface, so a key never sees more than the person who minted it.

First call

Make your first call

Start with a read. clients.list is safe to run as often as you like, returns real data, and proves Archie can see your workspace. It runs against https://api.dev.arch.ie once you mint a key. Create one in Dashboard → Keys, then the snippet below carries it for you. For now it reads $ARCHIE_API_KEY from your environment.

terminalbash

curl https://api.dev.arch.ie/api/v1/skills/clients.list/invoke \
  -H "Authorization: Bearer $ARCHIE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"limit": 5}'

What you get back:

responsejson

{
  "skill": "list_clients",
  "output": {
    "clients": [
      {
        "id": "8f2a1c44-1d2e-4b9a-9f3c-7e6b0a5d4c21",
        "name": "Cedar Park Holdings LLC",
        "jurisdiction": "US",
        "status": "active"
      }
    ],
    "total_count": 1,
    "has_more": false
  },
  "correlation_id": "corr_7Q2m..."
}

Every response carries the same envelope: the skill he ran, the typed output, and a correlation_id that links the call to its full audit trail. Log the correlation id so any answer is traceable back to the inputs behind it.

Want him to reason, not just read?

Send a query to messages.create (the ask_archie tool over MCP). He pulls the standard for Cedar Park Holdings LLC's jurisdiction (ASC 606 for revenue), runs the right specialist, and returns an answer cited to the subsection he relied on.

terminalbash

curl https://api.dev.arch.ie/api/v1/skills/messages.create/invoke \
  -H "Authorization: Bearer $ARCHIE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "Under ASC 606, when is revenue recognized on a usage-tiered SaaS contract?"}'

Authentication

OAuth 2.1, API keys, and the session path in detail.

Claude Connector

Every client config, with the correct schema each.

Tool catalog

Everything Archie can run, annotated read-only or write.

REST API

The full reference with runnable samples.

Sign in

Connect your client

Give Archie a task

Read the reply

Make your first call