---
name: agent-push-kit
description: Connect to Agent Push Kit and operate its complete notification product surface. Use when adding Agent Push Kit notifications to an application, sending or investigating events, managing customer accounts or members, creating or rotating ingestion credentials, connecting MCP or an SDK, registering devices, or changing service/type push preferences.
---

# Agent Push Kit

Use Agent Push Kit to add structured notifications to software, search the shared inbox, and administer the same product capabilities available in the human app.

## Start

1. Read `https://agentpushkit.com/llms.txt` for the live discovery map.
2. Prefer an existing `AGENT_PUSH_KIT_TOKEN` containing an `apt_` agent token. Never print, commit, or place it in a URL.
3. If no agent token exists, follow [references/account-bootstrap.md](references/account-bootstrap.md).
4. Prefer MCP for interactive agent work, an SDK for application code, and direct REST for a small integration or unsupported language.

## Choose the workflow

- Account, membership, token, or ingestion-key work: read [references/accounts-and-keys.md](references/accounts-and-keys.md).
- Add Agent Push Kit to an application: read [references/application-integration.md](references/application-integration.md).
- Construct and send events: read [references/sending-events.md](references/sending-events.md).
- Search or investigate the inbox: read [references/investigating-events.md](references/investigating-events.md).
- Change push delivery: read [references/notification-preferences.md](references/notification-preferences.md).
- Install or configure MCP or an SDK: read [references/mcp-and-sdks.md](references/mcp-and-sdks.md).

## Operating rules

- Treat `apk_` keys as application-ingestion credentials and `apt_` tokens as full user-level agent credentials.
- Select the intended customer account before every organization-scoped operation.
- Use stable exact notification types; do not invent multiple classification fields.
- Put service-specific detail in the single `metadata` object.
- Add a stable `externalId` whenever a source operation may retry.
- Rotate an ingestion key only when requested or genuinely required; rotation invalidates the prior key immediately.
- State the affected customer account before destructive account deletion or secret rotation.
- Remember that notification preferences stop future pushes only. Muted events remain searchable in the inbox.

The canonical API contract is `https://agentpushkit.com/openapi.json`.