Auth whoami
Inspect the current authenticated identity
Endpoint and authentication
https://mcp.swamix.com/api/tools/callKeep programmatic credentials in a server-side secret manager. Browser users authenticate with email sessions; this page never asks for a credential.
Send the tool name and an arguments object. Unknown fields should be rejected before they reach production.
Reuse one operation key when retrying paid or asynchronous work after a timeout.
Call auth_whoami
curl -sS https://mcp.swamix.com/api/tools/call \
-X POST \
-H "Authorization: Bearer $SWAMIX_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "auth_whoami",
"arguments": {}
}' Set SWAMIX_API_KEY in the process environment. The examples contain placeholders only and never store or transmit a secret from this page.
Arguments
Send an empty arguments object. The live schema will appear here when this tool publishes inputs.
Read the result
Successful calls return a JSON envelope. Treat the result as tool-specific data and preserve the HTTP status when logging failures.
{
"result": {
"tool": "auth_whoami",
"status": "success",
"data": "tool-specific response"
}
} Know what to do next
The tool name or arguments do not match the published schema.
Use a server-side programmatic credential or an authenticated email session.
The account balance cannot cover this operation.
The account is not allowed to access this tool. Admin tools require admin access.
The route or tool name does not exist.
Reduce the request or use the supported asset flow.
Back off using response guidance; do not hot-loop retries.
Retry safe work with bounded backoff and preserve idempotency for media.