Skip to content

Local API and Security

Jump to bottom
Manit Arora edited this page Oct 21, 2026 · 1 revision

Local API and Security

AXIOM's HTTP interface is intended for local workspace integration. The standalone daemon and the Control Center workspace API are local services, not an AXIOM-hosted backend.

Starting the daemon

axiom daemon --host 127.0.0.1 --port 0

Port 0 asks the operating system to select an available port. AXIOM prints the loopback URL for the running daemon. Example read-only routes include:

GET /health
GET /api/info
GET /api/summary
GET /api/actions
GET /api/hardware
GET /api/tools

Consult docs/API.md and the live /api/openapi.json document from the running daemon for the current API contract.

Network exposure

The default bind is loopback-only. A non-loopback bind is rejected unless network access is explicitly enabled using --allow-network.

Enabling network access is a meaningful change to the threat model. Only do it after evaluating firewall rules, trusted clients, authentication needs, and the sensitivity of the workspace. Do not assume a local service is safe to expose simply because it was designed for localhost.

API Playground guardrails

The beta.4 API Playground uses:

  • a fixed allowlist of GET endpoints;
  • request timeouts;
  • bounded response reads;
  • capped response previews;
  • clear limits that discourage treating the UI as an arbitrary HTTP client.

It is not designed to fetch arbitrary URLs or issue mutating HTTP methods. CLI-only commands are not secretly executed by clicking an explorer entry.

Diagnostics and privacy

Support bundles are designed to exclude credentials, environment-variable values, configuration contents, model weights, datasets, logs, experiment records, user-authored data, and absolute paths. They still contain limited metadata, so inspect the ZIP before sharing it.

MCP is a separate interface

axiom mcp serve exposes a stdio integration path for an MCP client; it is separate from the HTTP daemon. MCP tools are denied by default. Inspect the active policy and grant the smallest set of tools required by the client.

Report a security concern

Do not post credentials, exploit details against a live system, or sensitive logs in a public issue. Follow the repository's Security policy for the available reporting route.

AXIOM AI source repository · Issues · MIT license

Clone this wiki locally