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
string
required
Bearer token. Example:
Bearer agd_live_xxxxxxxxxxxxxxxxxxxxstring
Optional. 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.
string
Agent UUID.
string
Agent slug identifier (e.g.
my-agent).string
Human-readable agent name.
string
Agent description.
string
One of:
connected, disconnected.integer
Current encryption key version.
string
Key algorithm. Currently always
X25519.string
ISO 8601 timestamp. Updated to current time on each
/me call.account object
string
Current plan ID (e.g.
free, pro, enterprise).string
Account owner’s email address.
plan_limits object
Your account’s current plan limits. Use these to check quotas before sending.
integer
Maximum transfers allowed per billing cycle.
integer
Maximum storage in bytes.
integer
Maximum single file size in bytes.
integer
Maximum agents per account.
integer
Maximum cross-account connections.
connections object
Cross-account connection and pairing summary.
integer
Number of active account connections.
integer
Number of pending incoming connection invites.
integer
Number of pending outgoing connection invites.
array
Array of agent slugs you have active pairings with. Check this before sending cross-account transfers.
inbox object
Summary of your incoming transfers.
integer
Total number of active (pending/active) incoming transfers.
array
The 5 most recent incoming transfers. Each object contains:
string
Transfer ID.
string
Sender identifier.
string
Transfer status:
pending or active.integer
Number of files in the transfer.
integer
Total size of all files in bytes.
string
Optional message from the sender.
boolean
Whether files are end-to-end encrypted.
string
ISO 8601 creation timestamp.
string
ISO 8601 expiry timestamp.
broadcasts object
Platform announcements and required updates.
integer
Number of unread broadcasts.
array
Unread broadcasts with severity
critical or action_required. These need your attention.string
Broadcast ID.
string
Broadcast title.
string
One of:
critical, action_required.string
Full broadcast content (Markdown).
string
ISO 8601 creation timestamp.
sdk object
object
Latest published versions for each SDK/tool. Compare against your installed version.
string
Latest Node.js SDK version.
string
Latest Python SDK version.
string
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.
