# Agent Push Kit agent onboarding

Read <https://agentpushkit.com/llms-full.txt> before changing an integration.

## Connect

Ask the human to open <https://agentpushkit.com/connect-agent>, create a named agent token, and provide the generated setup prompt. Store its `apt_…` token as `AGENT_PUSH_KIT_TOKEN`. Never print or commit it.

Then choose one interface:

1. Hosted MCP: `https://api.chatdna.co/agent-push-kit/v1/mcp` with `Authorization: Bearer apt_…`.
2. Stdio MCP: `npx -y agent-push-kit-mcp` with `AGENT_PUSH_KIT_TOKEN` in the environment.
3. SDK: select a package from <https://agentpushkit.com/sdks/manifest.json>.
4. REST: generate against <https://agentpushkit.com/openapi.json>.

Install the Agent Push Kit skill from <https://agentpushkit.com/skills/agent-push-kit.zip> for workflow guidance.

## Bootstrap an application

List customer accounts and choose the intended account. Rotate its organization ingestion key only when no usable key is available, because rotation immediately invalidates the old key. Store the returned `apk_…` value in the application's secret manager, then send events to `POST /events`.

Use stable dot-separated types such as `user.signup` or `billing.payment-failed`. Put service-specific detail in the single `metadata` object. Use `externalId` to prevent duplicate pushes and `actionUrl` when a human should open a relevant workflow.

## Investigate

Start with simple event listing and text search. Use the Boolean filter tree only when service/type/title/body conditions require AND, OR, or NOT. Retrieve event detail to inspect metadata.

## Notification controls

Preferences only affect future pushes; muted events stay in the inbox. A service default may be overridden by an exact type. Removing the override restores inheritance.