Get an X profile

Get an X profile

Returns one public X profile with bio, follower and following counts, verification, location, and any email, phone numbers or links the profile publishes.

Note: 1 credit per call. id takes a numeric user ID, a username with or without @, or a URL-encoded profile URL; a number is always read as a user ID.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "xquik": { "url": "https://xquik.com/mcp?codemode=false" } } }

Call the MCP tool getUser.

Server URL: https://xquik.com/mcp?codemode=false

Note: Native mode: one tool per API operation, named by its OpenAPI operationId. The plain https://xquik.com/mcp is Code Mode, with only docs, search, execute and whoami. Tools list before sign-in; the first tool call starts the OAuth sign-in.

API (official)

• Base URL: https://xquik.com/api/v1
• Endpoint: GET /x/users/{id}
• Auth: send the header x-api-key: $XQUIK_API_KEY
• Get a key: https://dashboard.xquik.com/en/api-keys
• Docs: https://docs.xquik.com/api-reference/overview

Note: Public reads need no X account; posting, DMs and private reads need one connected in the dashboard. Calls spend credits and a 402 means the balance is too low. A key always has the read scope; monitors and writes need their scopes added on the key.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.