# Aient > Aient integration docs for telemetry, source maps, webhooks, and event schemas. ## Docs - [Agent purchase and configuration](https://docs.aient.ai/agent-commerce.md): How agents buy and configure Aient through Stripe Checkout, provisioning sessions, scoped permissions, spend caps, and webhook entitlement reconciliation. - [Use Aient docs from AI assistants and coding agents](https://docs.aient.ai/ai-tools.md): Point Cursor, Claude Code, and other AI tools at Aient docs through generated Markdown, llms.txt, and skill.md so agents instrument apps from the same source. - [Aient integration docs](https://docs.aient.ai/index.md): Connect apps to Aient with OpenTelemetry SDKs, source map uploads, OTLP ingest endpoints, and CloudEvents webhooks for problem lifecycle events. - [Common questions about Aient](https://docs.aient.ai/questions.md): Answers to common questions about what Aient does, how it ingests OpenTelemetry signals, groups problems, integrates Slack and GitHub, and drives remediation. - [Browser telemetry quickstart](https://docs.aient.ai/quickstart/browser.md): Install @aient/otel-browser, register it at app boot with a publishable key, and send frontend traces and logs to Aient with release metadata for source maps. - [Server telemetry quickstart](https://docs.aient.ai/quickstart/server.md): Install @aient/otel and initialize it before HTTP, database, or queue clients to send Node.js traces and logs to Aient with service name and release metadata. - [Event registry](https://docs.aient.ai/reference/event-registry.md): Aient publishes webhook event schemas at registry.aient.ai with immutable schema artifact URLs and versioned event aliases for generated clients and browsing. - [OpenTelemetry endpoints](https://docs.aient.ai/reference/otlp-endpoints.md): Public OTLP HTTP endpoints for traces and logs at ingest.aient.ai, bearer token auth with publishable keys, and resource attributes Aient uses for grouping. - [@aient/otel-browser SDK reference](https://docs.aient.ai/reference/sdk-browser.md): Configuration options for @aient/otel-browser including publishable key, service name, release metadata, and exporter URL overrides for browser telemetry. - [@aient/otel SDK reference](https://docs.aient.ai/reference/sdk-server.md): Configuration options for the @aient/otel Node.js package including publishable key, service name, release metadata, and exporter URL and header overrides. - [@aient/sourcemaps CLI reference](https://docs.aient.ai/reference/sourcemaps-cli.md): Command line options for the aient-sourcemaps upload command including service name, commit SHA, glob pattern, bundle prefix, concurrency, and dry run. - [Upload source maps](https://docs.aient.ai/source-maps/upload.md): Upload JavaScript source maps from CI with @aient/sourcemaps so Aient resolves minified browser stack frames using matching service name and commit SHA. - [integration.linear.connected](https://docs.aient.ai/webhooks/events/ai.aient.integration.linear.connected.md): CloudEvent fired when a Linear workspace connection becomes usable, with payload fields for organisationId, workspaceId, and workspaceName. - [integration.slack.connected](https://docs.aient.ai/webhooks/events/ai.aient.integration.slack.connected.md): CloudEvent fired when a Slack workspace connection becomes usable for Aient notifications, with payload fields organisationId, workspaceId, and workspaceName. - [integration.slack.notification_channel_selected](https://docs.aient.ai/webhooks/events/ai.aient.integration.slack.notification_channel_selected.md): CloudEvent fired when a tenant selects a Slack channel to receive Aient notifications, with payload fields channelId, channelName, and organisationId. - [onboarding.completed](https://docs.aient.ai/webhooks/events/ai.aient.onboarding.completed.md): CloudEvent fired when a tenant finishes Aient onboarding, with payload fields organisationId and onboardingRunId emitted from the onboarding bounded context. - [organisation.created](https://docs.aient.ai/webhooks/events/ai.aient.organisation.created.md): CloudEvent fired when a tenant organisation is created in Aient, with payload fields organisationId, organisationName, and ownerUserId for provisioning. - [problem.closed](https://docs.aient.ai/webhooks/events/ai.aient.problem.closed.md): CloudEvent fired when an Aient problem is closed, with payload fields organisationId, problemId, and closureReason for tracking lifecycle outcomes. - [problem.detected](https://docs.aient.ai/webhooks/events/ai.aient.problem.detected.md): CloudEvent fired when Aient detects a new problem from grouped telemetry, with payload fields organisationId, problemId, environmentId, severity, and title. - [problem.regressed](https://docs.aient.ai/webhooks/events/ai.aient.problem.regressed.md): CloudEvent fired when a previously closed Aient problem regresses, with payload fields organisationId, problemId, and previousStatus for routing. - [problem.triaged](https://docs.aient.ai/webhooks/events/ai.aient.problem.triaged.md): CloudEvent fired when Aient triages a detected problem, with payload fields organisationId, problemId, triageId, and severity for downstream routing. - [remediation.investigation_completed](https://docs.aient.ai/webhooks/events/ai.aient.remediation.investigation_completed.md): CloudEvent fired when a remediation investigation completes, with payload fields problemId, investigationId, confidence, and shouldRemediate flag. - [remediation.pr_created](https://docs.aient.ai/webhooks/events/ai.aient.remediation.pr_created.md): CloudEvent fired when Aient opens a remediation pull request, with payload fields problemId, pullRequestUrl, repositoryFullName, and PR status. - [remediation.verified](https://docs.aient.ai/webhooks/events/ai.aient.remediation.verified.md): CloudEvent fired when an Aient remediation is verified against telemetry, with payload fields problemId, remediationId, and verificationId for closure. - [repository.discovered](https://docs.aient.ai/webhooks/events/ai.aient.repository.discovered.md): CloudEvent fired when Aient discovers a tenant repository through GitHub, with payload fields organisationId, repositoryFullName, and repositoryId. - [team.invitation_accepted](https://docs.aient.ai/webhooks/events/ai.aient.team.invitation_accepted.md): CloudEvent fired when a teammate accepts an Aient team invitation, with payload fields invitationId, memberUserId, and organisationId. - [Webhook event schemas](https://docs.aient.ai/webhooks/events/index.md): Index of tenant-selectable Aient webhook events covering problem lifecycle, remediation, integrations, onboarding, and repository discovery with schema links. - [Aient webhooks overview](https://docs.aient.ai/webhooks/overview.md): Aient delivers tenant-selectable events as CloudEvents 1.0 structured JSON with at-least-once delivery and idempotency through source and id tuples. - [Webhook signing](https://docs.aient.ai/webhooks/signing.md): Verify Aient webhook signatures using the raw request body and endpoint secret, reject stale or malformed signatures, and deduplicate events before processing. ## OpenAPI Specs - [openapi](https://docs.aient.ai/api-reference/openapi.json)