Axiom

Name: Axiom API
Brand: Axiom
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilityoauth2, apiKey, bearer76 EndpointsREST

For Agents

Ingest events into Axiom, run APL or aggregation queries over log data, and manage monitors, dashboards, and notifiers. Suited to agents that diagnose production issues from log evidence.

Quickstart

Get started with Axiom in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"query an axiom dataset"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Axiom API.

Ingest event payloads into a named Axiom dataset for log and metric storage

Run APL or aggregation queries over a dataset and return matched events

Create, update, and delete datasets and their virtual fields

Manage monitors that trigger on threshold or anomaly conditions over query results

Configure notifiers (Slack, email, webhook) that route monitor alerts onward

GET STARTED

Start building with Axiom API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Axiom, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Axiom, keeping it validated and agent-ready. Axiom is a cloud-native observability platform for ingesting, querying, and alerting on event data and logs. The v2 API exposes datasets, ingest, query, monitors, notifiers, dashboards, annotations, organisations, tokens, users, virtual fields, starred queries, and history endpoints, supporting both interactive analytics and automated pipelines. Authentication uses bearer tokens with a query-string token option for ingest.

Use Cases

Patterns agents use Axiom API for, with concrete tasks.

★ Centralised Log Ingestion

Engineering teams can ship application and infrastructure logs into Axiom by POSTing structured events to dataset-scoped ingest endpoints. The dataset CRUD endpoints under /datasets allow creation, trimming, and vacuuming so retention can be controlled. Suitable for teams consolidating logs from multiple services into a single queryable store.

POST a batch of JSON log events into an Axiom dataset and verify ingestion by running a count query over the last 5 minutes

Automated Incident Detection

Operations teams can codify alerting rules in Axiom by creating monitors that evaluate APL queries on a schedule and fire when thresholds are breached. Notifiers attached to monitors route alerts to Slack, PagerDuty, or webhooks. Useful for replacing ad-hoc threshold dashboards with versioned, programmatic rules.

Create an Axiom monitor that runs an APL query for error rate over 5xx responses and attach a Slack notifier so alerts post to the on-call channel

Ad-Hoc Log Investigation

On-call engineers can run APL queries directly against a dataset to investigate incidents, pivot into related events, and save useful queries as starred queries for reuse. Annotations let teams mark deploys or feature flips on the timeline. Suited to firefighting workflows where speed of search matters.

Run a query against an Axiom dataset for events where status >= 500 in the last 30 minutes and return the top 50 matches

Agent-Driven Log Triage via Jentic

An on-call agent can pull recent error events from Axiom, summarise them, and propose a remediation by chaining query, monitor, and dataset operations through Jentic. Jentic isolates the bearer token and exposes the operations as discoverable tools. Suited to incident copilots and SRE assistants.

Search Jentic for 'query axiom dataset', load the dataset query operation, and execute it to retrieve the last 15 minutes of error events for triage

Key Endpoints

76 endpoints — jentic publishes the only available openapi specification for axiom, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/datasets

List datasets

POST

/datasets

Create a dataset

POST

/datasets/{dataset_id}/trim

Trim a dataset by duration

GET

/datasets/{dataset_id}/fields

Get fields for a dataset

GET

/annotations

List annotations

POST

/annotations

Create an annotation

GET

/datasets

List datasets

POST

/datasets

Create a dataset

POST

/datasets/{dataset_id}/trim

Trim a dataset by duration

GET

/datasets/{dataset_id}/fields

Get fields for a dataset

GET

/annotations

List annotations

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Axiom bearer tokens are stored encrypted in the Jentic vault and attached as the Authorization header at call time. Ingest tokens used in the `tk` query parameter are equally vault-isolated. Agents never see the raw token.

Intent-based discovery

Agents search Jentic by intent (e.g. 'query axiom dataset' or 'create axiom monitor') and Jentic returns the matching Axiom operations with their input schemas, so the agent can act without crawling docs.

Time to first call

Direct Axiom integration: 1-2 days to wire bearer-token handling, dataset bootstrapping, and monitor/notifier configuration. Through Jentic: under 1 hour from search to first executed query.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Sentry API

Sentry focuses on application error monitoring with stack traces and release health.

Choose Sentry when the agent needs error grouping and release-health context; choose Axiom when the workflow is broad event and log analytics.

Alternative

Splunk API

Splunk offers enterprise log search and analytics as a competing observability platform.

Pick Splunk for enterprise SIEM scenarios; pick Axiom when the team prefers a cloud-native event-store priced on ingest.

Complementary

Better Stack API

Better Stack adds uptime monitoring and incident management on top of log sources.

Use Better Stack alongside Axiom when the team wants uptime checks and on-call schedules sitting in front of Axiom-stored logs.

FAQs

Specific to using Axiom API through Jentic.

Why is there no official OpenAPI spec for Axiom?

Axiom does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Axiom via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Axiom API use?

Axiom v2 supports HTTP bearer tokens for most operations and a query-string token (`tk`) on ingest endpoints. Through Jentic, these tokens are stored encrypted and attached to the request at call time so secrets never enter the agent context.

Can I create datasets and ingest events with the Axiom API?

Yes. POST /datasets creates a dataset and the ingest endpoints under the dataset path accept event payloads. Use POST /datasets/{dataset_id}/trim to control retention and POST /datasets/{dataset_id}/vacuum to reclaim space.

How do I create a monitor through the Axiom API?

Use the /monitors endpoints to create a monitor backed by an APL query, then attach a notifier so alerts route to Slack, email, or a webhook when the threshold is breached.

What are the rate limits for the Axiom API?

Axiom enforces plan-based ingest and query quotas rather than fixed per-endpoint limits. The OpenAPI spec does not declare numeric limits; check your Axiom plan for current ingest and query quotas.

How do I query a dataset through Jentic?

Search Jentic for 'query axiom dataset', load the dataset query schema, and execute it with your APL or aggregation query body. Jentic injects the bearer token and returns the matched events to your agent.