Your profile is the central record for your account — it holds your name, email, plan, credit usage, and the configuration that controls how the ManticScore AI agent behaves on your behalf.Documentation Index
Fetch the complete documentation index at: https://docs.manticscore.com/llms.txt
Use this file to discover all available pages before exploring further.
Read your profile
Update name or email
null for either field to leave it unchanged. The response has the same shape as GET /profile.
Configure agent autonomy
The agent autonomy setting controls how much the ManticScore AI acts on your behalf without stopping to ask for confirmation.agent_config object.
autonomy_level options
autonomy_level options
| Level | Behavior |
|---|---|
suggest | Agent proposes actions; you tap to confirm each one |
confirm | Agent requires explicit approval before acting |
auto | Agent acts immediately without asking |
auto_actions
auto_actions
You can allow specific actions to run automatically even when
autonomy_level is suggest or confirm. Pass an array of action strings:slack.postnotion.exportlinear.create_issuesjira.create_issuesgmail.sendgithub.create_pr
Link a phone number
Linking your phone number enables App Clip delivery over iMessage. When you link a number, ManticScore sends you a welcome App Clip to confirm the connection.verified: true means the welcome iMessage was successfully enqueued. Delivery typically takes 1–3 seconds when the system is idle.
Error responses:
| Status | Meaning |
|---|---|
422 | Invalid phone number format |
409 | Number is already linked to another account |
Each iMessage ManticScore sends contains exactly one App Clip URL. ManticScore does not send arbitrary text.
Manage MCP bearer tokens
If you connect to the MCP server from Claude Code, Claude Desktop, or any other agent that speaks the MCP HTTP transport, you authenticate with a per-user bearer token minted from your profile. Each token has the formmcp_<48 url-safe chars>. The plaintext is returned exactly once at creation; only the SHA-256 hash is stored server-side. If you lose a token, revoke it and mint a new one.
Create a token
Optional human-readable label to help you remember where the token is used (e.g.
Claude Code on laptop, agent-server). Stored but not validated.UUID of the token row. Use this with
DELETE /profile/mcp/tokens/{token_id} to revoke.Label as supplied at creation, if any.
The plaintext bearer token. Returned exactly once — store it immediately. ManticScore cannot recover it.
Insert timestamp as an ISO 8601 string in UTC.
List active tokens
revoked_at IS NULL, newest-first. Hashes and plaintext tokens are never returned — only metadata.
UUID of the token row.
Label as supplied at creation, if any.
Last time the token was used to authenticate an MCP request, as an ISO 8601 string in UTC.
null if the token has never been used.Insert timestamp as an ISO 8601 string in UTC.
Revoke a token
ok. Returns 404 if the token doesn’t exist or belongs to another account.
| Status | Meaning |
|---|---|
200 | Token revoked (or was already revoked). |
404 | Token not found, or not owned by the authenticated user. |
Bootstrap call
On app launch, you can hydrate your entire initial state with a single request instead of calling/profile, /secrets, and your subscription endpoint separately.