Skip to main content

What do I use as the API key in MCP or the LLM Gateway?

Use your project's API key alone for an API Key Only project, or add its secret for a Signature-Based project, as key:secret in one field or as two variables for local MCP.

Use your project's API key alone if the project is API Key Only, or YOUR_API_KEY:YOUR_API_SECRET if it's Signature-Based, where the key alone is rejected. Enter it as plain text with no encoding.

  • LLM Gateway: paste it into your tool's API key field. Most tools then send the Authorization: Bearer header for you.

  • Hosted MCP: add it to your client's config as the Authorization header: Bearer, a space, then your credential.

  • Local MCP: set WIRO_API_KEY, plus WIRO_API_SECRET for Signature-Based, as separate environment variables.

You never add x-signature or x-nonce headers yourself. You get the key and secret when you create a project. To see them again, open the Projects page, click the eye icon next to the API secret and confirm it's you with your password or a code we e-mail you (see our API key guide). For a team project, only team admins and the organization owner can see the secret. Keep them out of browser code and shared config files.

In MCP, "...is not founded" means a wrong key, "...is not valid" a wrong secret, and "requires signature authentication" a missing secret. Details: MCP guide and LLM Gateway guide.

Did this answer your question?

Related Articles