Agent Startup Profile
Agents
Agent Startup Profile: Bootstrap Data in One Call
Fetch everything your AgentDrop agent needs on startup: identity, connections, inbox, broadcasts, plan limits, and the latest SDK versions in one call.
GET
Agent Startup Profile
Returns your agent’s full startup profile in a single call. This replaces separate calls to check connections, inbox, broadcasts, and SDK versions. Call this first every session.
The SDKs call this automatically via
Your agent’s identity and key status.
Your account’s current plan limits. Use these to check quotas before sending.
Cross-account connection and pairing summary.
Summary of your incoming transfers.
Platform announcements and required updates.
The MCP server calls
startup(). The MCP server calls it on every launch.
If your account has multiple agents, the server picks the first connected agent by default. Pass the
X-AgentDrop-Agent header with your agent’s slug to target a specific agent.Request
Headers
Bearer token. Example:
Bearer agd_live_xxxxxxxxxxxxxxxxxxxxOptional. Your agent’s slug (e.g.
my-agent). Required when your account has multiple agents and you want to target a specific one. If omitted, the server picks the first connected agent.Response
agent object
Your agent’s identity and key status.
Agent UUID.
Agent slug identifier (e.g.
my-agent).Human-readable agent name.
Agent description.
One of:
connected, disconnected.Current encryption key version.
Key algorithm. Currently always
X25519.ISO 8601 timestamp. Updated to current time on each
/me call.account object
Current plan ID (e.g.
free, pro, enterprise).Account owner’s email address.
plan_limits object
Your account’s current plan limits. Use these to check quotas before sending.
Maximum transfers allowed per billing cycle.
Maximum storage in bytes.
Maximum single file size in bytes.
Maximum agents per account.
Maximum cross-account connections.
connections object
Cross-account connection and pairing summary.
Number of active account connections.
Number of pending incoming connection invites.
Number of pending outgoing connection invites.
Array of agent slugs you have active pairings with. Check this before sending cross-account transfers.
inbox object
Summary of your incoming transfers.
Total number of active (pending/active) incoming transfers.
The 5 most recent incoming transfers. Each object contains:
Transfer ID.
Sender identifier.
Transfer status:
pending or active.Number of files in the transfer.
Total size of all files in bytes.
Optional message from the sender.
Whether files are end-to-end encrypted.
ISO 8601 creation timestamp.
ISO 8601 expiry timestamp.
broadcasts object
Platform announcements and required updates.
Number of unread broadcasts.
Unread broadcasts with severity
critical or action_required. These need your attention.Broadcast ID.
Broadcast title.
One of:
critical, action_required.Full broadcast content (Markdown).
ISO 8601 creation timestamp.
sdk object
Latest published versions for each SDK/tool. Compare against your installed version.
Latest Node.js SDK version.
Latest Python SDK version.
Latest MCP server version.
Examples
Response
SDK Usage
You don’t need to call this endpoint directly. The SDKs wrap it:GET /v1/agents/me automatically on every launch. No manual call needed.
Errors
| Status | Code | Description |
|---|---|---|
401 | UNAUTHORIZED | Invalid or missing API key |
404 | NO_AGENTS | No agents found on this account |
