Axiom through Squiid

What Axiom is

Axiom is a logging and event platform designed to make keeping everything affordable. Data is ingested through HTTP, OpenTelemetry or integrations with hosts like Vercel and Cloudflare, stored in a columnar format, and queried with the Axiom Processing Language for filtering, aggregation and joins. Dashboards and monitors run on the same queries, and there is no sampling requirement, so the event you need is still there when you go looking. Datasets are separated by purpose, so application logs, model calls and platform events can have different retention.

For AI-coded apps this is where prompt and response logs, model latency, token counts and job outcomes belong. Those records are high volume and mostly boring until something misbehaves, at which point being able to query three weeks of them matters. Traditional log vendors price that behaviour out; Axiom is one of the services that makes it reasonable to log every model call with its inputs. Structured fields make queries far more useful than text search, which is worth planning before the first log line is written.

Why connect it through Squiid

Axiom is on the Squiid roadmap. When it lands, Squiid will provision the organization, hold the API token and route ingest and query calls through https://api.squiid.io/v1/axiom/... with Authorization: Bearer $SQUIID_API_KEY, with SDKs working by base URL swap (gateway convention). Ingested volume and retention will bill at Axiom's listed price on one Squiid invoice, next to the model spend those logs describe. Monitors can alert on a query result, which turns a log pattern into a notification without a separate alerting tool.

• One account, one key, one bill, one dashboard. Axiom sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Axiom credentials. Your code carries SQUIID_API_KEY, so AXIOM_TOKEN, AXIOM_ORG_ID, AXIOM_DATASET never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Axiom costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Axiom organization with tokens held by Squiid
• Log, trace and event ingest without sampling
• APL queries, dashboards and monitors
• OpenTelemetry and platform integrations
• Axiom list pricing, no markup

How to connect Axiom

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces AXIOM_TOKEN, AXIOM_ORG_ID, AXIOM_DATASET
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/axiom/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Axiom charges by ingested data volume and retention on plan tiers, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Axiom usage, with no markup and no per-request margin.

Axiom has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Axiom usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: historical data is exported where Axiom supports it and the project is re-created in your own account, with new events going to your own keys. Squiid never owns your code, your schema or your domain, and the gateway speaks Axiom's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Axiom through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Axiom usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.