Agents
Aient for agents
Give Codex, Claude Code, Cursor, and your own agents structured ways to connect Aient, instrument services, receive events, and prepare remediation work without blurring human approval points.
principal: oauth_mcp: available x402_wallet: beta context: telemetry: required source_maps: browser_only webhooks: signed_cloudevents human_approval: - github_install - slack_workspace - payment_authority - pr_merge
Agent-ready surfaces
MCP onboarding
Connect Aient to an existing human-owned organisation and let agents finish scoped activation steps.
x402 agent commerce
Use wallet-paid provisioning and paid calls while keeping install consent and spending authority explicit.
SDK instrumentation
Install server and browser telemetry so Aient can detect production issues with useful context.
Webhooks
Receive signed CloudEvents for problem, remediation, and integration automation.
API reference
Stable REST references still need a generated public contract; MCP tools and events stay separate.
Agent skill
Mintlify can expose agent-readable docs; a custom Aient setup skill should wait until docs stop drifting.
Rapid onboarding path
- 1Pick the principal: OAuth organisation, wallet-paid x402, or normal SaaS account.
- 2Attach the right context: MCP tools, SDK telemetry, source maps, and repository access.
- 3Validate readiness: a service emits telemetry, docs links resolve, and the agent can prepare scoped remediation work.
Humans still approve
What agents can start today
The fastest path is instrumentation first, then repository access, then a scoped remediation workflow once Aient can see a real signal.