Axiom MCP integration for AI agents.
Connect AI agents to Axiom through 5 structured actions, including get dataset, create dataset, and delete dataset. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Axiom integration exposes
The Axiom Agent App exposes 5 provider-backed actions for data and developer tools work. Its current contract lets an authorized agent get an axiom dataset by id or unique name, create an axiom dataset, and delete an axiom dataset by id or unique name. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Axiom account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Axiom capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_datasetREADGet an Axiom dataset by ID or unique name.
INPUTS: dataset_id
create_datasetWRITECreate an Axiom dataset.
INPUTS: name / description / edgeDeployment / kind / retentionDays
delete_datasetHIGH IMPACTDelete an Axiom dataset by ID or unique name.
INPUTS: dataset_id
list_datasetsREADList Axiom datasets visible to the current token.
run_apl_queryREADRun an Axiom Processing Language query through the global API endpoint.
INPUTS: apl / format / nocache / saveAsKind / dataset_name
INPUT CONTRACTS
Know what the action needs before it runs.
get_dataset
dataset_idOPTIONAL- The Axiom dataset ID or unique dataset name.
create_dataset
nameREQUIRED- The unique Axiom dataset name.
descriptionOPTIONAL- The dataset description.
edgeDeploymentOPTIONAL- The edge deployment assigned to the dataset.
kindOPTIONAL- The Axiom dataset kind.
retentionDaysOPTIONAL- The number of days Axiom should retain data in the dataset.
delete_dataset
dataset_idOPTIONAL- The Axiom dataset ID or unique dataset name.
run_apl_query
aplREQUIRED- The APL query string to execute.
formatOPTIONAL- The Axiom query result format.
nocacheOPTIONAL- Whether Axiom should bypass cached query results.
saveAsKindOPTIONAL- The saved query result kind.
dataset_nameOPTIONAL- The associated dataset name when saving query results.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Dataset
Get an Axiom dataset by ID or unique name. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_datasetControl Create Dataset
Create an Axiom dataset. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_datasetVerify with List Datasets
List Axiom datasets visible to the current token. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_datasetsSAFETY BOUNDARY
Operate Axiom with explicit limits
- Authorize Axiom with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_dataset` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Axiom rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Axiom task completed successfully.
CONNECTION MODEL
API key
Axiom API token used with the Authorization Bearer header. Create or view API tokens from Settings > API tokens in Axiom: https://app.axiom.co/
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Axiom.