Archon.tools / Developer preview

Your workspace.
Your choice of intelligence.

Bring your own assistant or build an app around your business. The official Archon API and MCP use the same workspace permissions, so your connection stays under your control.

Customer activation is being qualified.

The first release provides read-only workspace and setup access. Create keys in your account when Connections is enabled for your workspace.

Open account connections →See how it connects ↓

One permission model

Two interfaces.
One connected workspace.

01 / API

Build your own connection

Use standard HTTPS requests with a workspace API key in the Authorization header. Keep credentials on your server or in a secure local client.

/api/workspace/v1

02 / MCP

Bring your own assistant

Connect an MCP client that supports remote Streamable HTTP and a custom authorization header. The assistant discovers the operations your key is permitted to use.

/mcp

Browser-only connectors that require OAuth aren’t supported by this key-based preview. MCP support depends on your client, its plan and administrator settings. This is Archon’s own service; a direct LeadConnector connection has separate permissions and controls.

Connect in your account

Give your assistant
the access you choose.

Name the connection
Sign in to your Archon.tools account with your plan’s email. Open API & AI connections in your active workspace account.
Choose permissions and expiry
Workspace identity is included. Add your setup checklist and tool guides if needed. Pilot keys last up to 30 minutes within your workspace’s approved access window of up to one hour. The underlying 90-day storage ceiling does not extend pilot access.
Save the key once
Put it in your client’s secure credential settings or a secret manager. Keys are shown once. Don’t paste one into an LLM conversation, a URL, a public repository or a browser app.
Start with a small read
Ask for the connected workspace and its selected tools. Check the result, then request your setup guides. Revoke the connection from your account whenever you need to.

Initial capabilities

Useful context.
Deliberate permissions.

What your client can read	API	MCP tool / permission
Your workspace ID, selected tools and permitted operations	`GET /workspace`	`workspace_describe` workspace:read
Setup guides and progress you’ve marked for your selected tools	`GET /setup-guide`	`setup_guide_read` setup:read

API paths above are relative to https://archon.tools/api/workspace/v1. Customer conversations, contact records, appointment records, messages, billing changes and administrative actions are outside this preview. Further workspace operations require separate qualification.

Requests check current workspace access, key permissions, expiry and revocation. Scheduled cancellation keeps eligible access through the current trial or paid period; access stops when that period ends. Revoking a key stops that connection immediately.

Read the API schema →

For developers

Connect with a few lines.

These examples apply after your workspace connection is enabled. Set the environment variable securely outside your code. Both examples use the same key.

REST / Node.js

// Set ARCHON_WORKSPACE_API_KEY in your local secret manager.
const apiKey = process.env.ARCHON_WORKSPACE_API_KEY;
if (!apiKey) throw new Error("Set your workspace key first");
const response = await fetch("https://archon.tools/api/workspace/v1/workspace", {
  headers: { Authorization: `Bearer ${apiKey}` },
});
if (!response.ok) throw new Error(`Workspace request: ${response.status}`);
console.log(await response.json());

MCP / Node.js

// Uses @modelcontextprotocol/sdk 1.32.1 in Node.js.
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const apiKey = process.env.ARCHON_WORKSPACE_API_KEY;
if (!apiKey) throw new Error("Set your workspace key first");
const client = new Client({ name: "my-workspace-assistant", version: "1.0.0" });
const transport = new StreamableHTTPClientTransport(new URL("https://archon.tools/mcp"), {
  requestInit: { headers: { Authorization: `Bearer ${apiKey}` } },
});
try {
  await client.connect(transport);
  console.log(await client.listTools());
  console.log(await client.callTool({ name: "workspace_describe", arguments: {} }));
} finally {
  await client.close();
}

The preview uses the official TypeScript MCP SDK 1.32.1 and protocol version 2025-11-25. Your client must support a compatible protocol version and authorization headers.

Your connection. Your control.

A key for each assistant.
A stop button for each key.

Bounded usage

Connections share your workspace’s usage limits. REST rate limits return HTTP 429 with Retry-After guidance; MCP calls return a structured limit error. Clients should wait and avoid automatic retry loops. Pilot access and commercial terms are confirmed before activation; unlimited usage isn’t offered here.

Privacy and revocation

Your chosen model provider receives the information your client requests and may bill separately. Review its privacy settings. Signing out of your account doesn’t revoke saved API keys; revoke them in Connections.

Lost a key? Revoke it and create a replacement. If a creation or revocation result is uncertain, use Check result and keep the operation ID; don’t repeat the change. A lost one-time key cannot be redisplayed.

Manage connections →Explore tool guides →

Your workspace.Your choice of intelligence.

Two interfaces.One connected workspace.

Build your own connection

Bring your own assistant

Give your assistantthe access you choose.

Name the connection

Choose permissions and expiry

Save the key once

Start with a small read

Useful context.Deliberate permissions.