What is Axiom

Sectigo Axiom lets customer and partner AI agents use a provider's APIs and MCP tools for consequential writes. It gives each write narrow delegated authority, human approval in the customer's own workflow, exactly-once execution, and receipts that both parties can verify independently.

A SaaS application often knows which employee signed in. It still lacks four facts before it can accept an agent's request:

1. Who operates this agent?
2. Which customer delegated authority to it?
3. Does that authority cover this action against this resource?
4. If the agent loses its connection, did the receiving system commit the change?

Axiom records the answers to all four for every protected action.

Two products, one platform

Axiom Gateway and Axiom Control use the same identities, policies, action IDs and receipt format.

Capability	Axiom Gateway (developers)	Axiom Control (enterprise)
Entry point	Create a project, connect one API route or MCP tool, and see the first decision in the developer console.	Verify the organisation, invite existing projects, enroll gateways and preview enterprise policy.
Deployment	Sectigo-hosted proxy (HTTP and MCP), SDK embedded in the application, or an existing API gateway adapter.	Hosted management with customer-hosted enforcement.
Identity and permissions	Tenant-scoped agent registration, proof-of-possession credentials, narrow grants, layered policy.	Organisation verification, delegated administration, enterprise policy, emergency suspension and revocation tracking.
Approvals	Built-in approval page, mandatory or conditional approval, status and authenticated resume.	Customer-selected approval systems (ServiceNow first), separation of duties, linked decision evidence.
Evidence and operations	Project dashboard, policy simulator, structured decision reasons, signed receipts, SDK and CLI.	Cross-project search with access controls, evidence export, incident timelines, SIEM delivery and fleet health.

The free public services stand on their own and need no account: the Agent identity check, the MCP tool and skill change monitor and the receipt verifier.

The launch demonstration

A customer's billing agent asks Acme Billing for a USD 25,000 refund against invoice 417.

1. The provider protects the refund. Acme Billing maps its refund endpoint (POST /v1/invoices/{resource_id}/refunds) and its issue_refund MCP tool to one operation, billing.refund.create, with three material fields: amount, currency and beneficiary.
2. The customer admits the agent. The customer's tenant admin registers the billing agent, binds its key with proof of possession, and grants it billing.refund.create on invoices. The grant allows refunds up to USD 500 and requires a finance_approver above that. A hard ceiling denies anything above USD 100,000, even with approval.
3. Gateway evaluates the request. The agent authenticates (private key JWT plus DPoP) and submits. Gateway records a durable action in pending_approval. Nothing has reached the provider.
4. Finance approves the exact refund. The approver sees the tenant, invoice, amount, currency, beneficiary and requesting agent on the Axiom approval page or in ServiceNow. The decision is bound to the request digest. Approving records a decision; it never executes anything.
5. The original agent resumes. A status read or a signed wake event tells the agent the action is approved. It resumes with the same action ID and the same approved fields. Gateway rechecks the grant and policy, claims execution once and dispatches.
6. The provider commits once and signs. Acme Billing commits the refund atomically with the operation key and returns a signed axiom.outcome.v1 attestation. Axiom issues a receipt that links grant, approval, dispatch and outcome. The customer verifies it offline.

The same interaction works through the REST API, the hosted HTTP proxy and MCP. apps/api/test/launch-demo.test.ts runs it end to end.

Customer agent ──► Axiom Gateway or embedded SDK
                     │  approval required
                     ▼
                   Approval service (Gateway) or Axiom Control ──► approval page or customer workflow
                     ▲                                                │ authenticated decision
                     └────────────────────────────────────────────────┘
                     │  decision available (status read or wake event)
                     ▼
Customer agent ──► resume ──► Gateway claims execution once ──► receiving application
                                                                   │ signed outcome
                                                                   ▼
                                          signed action receipt (grant, approval, dispatch, outcome)

In standalone Gateway the project's approval service handles the approval handoff. In an enterprise deployment Control can route it through an external system. Either way the provider's application owns the business commit.

Where things run

Host	Serves
api.sectigoaxiom.com	REST API /v1/*, OAuth 2.1 authorization server, JWKS, well-known metadata
gw.sectigoaxiom.com	Hosted Gateway proxy: /p/{project_id}/http/* and /p/{project_id}/mcp
mcp.sectigoaxiom.com	Axiom MCP server (/mcp), OAuth-protected
app.sectigoaxiom.com	Developer console, Control, approval pages
sectigoaxiom.com	Landing page, the three free public services, sign-in
sample.sectigoaxiom.com	Acme Billing sample provider used by the quickstart (synthetic data)

In local development the API runs on http://localhost:8787 with the gateway under /gw and the MCP server at /mcp; the sample provider runs on :8788 and the console on :5173.

Preview status

This is a developer preview. Some pieces are simulated today:

• Sectigo Certificate Manager runs in mock mode, backed by a local development CA that issues real X.509 certificates, until SCM credentials are configured.
• Approval connectors: ServiceNow is the only connector that implements request and readback. Every other catalog entry declares its operations but has no working decision workflow. Simulated mode exercises the real webhook and readback path; no connector is qualified against a real customer tenant.
• Card checkout is not connected. Plan limits and spend limits are real.
• Customer-hosted gateway: Control can register gateways, sign policy bundles and move the executor flag, but the customer-hosted gateway runtime itself is not part of this repository.

Next steps

• First ten minutes: run the launch demonstration against the sample provider.
• Protect my service: choose between the proxy, the embedded SDK and an existing gateway.
• Action state machine: what each state means and what to do.