Spaces

What is a bearer token?

A bearer token is a secret code that a program sends with each request to prove it is allowed in, like a key card that opens any door it fits.

In plain words

A key card at a hotel does not check your face. Whoever holds the card gets into the room. A bearer token works the same way. The word "bearer" simply means whoever bears, or carries, it is let in.

That is simple and handy, and it is also why you treat the code like a card, not like a note you leave on the desk. Do not post it in a chat, a public page or a shared document.

If it ever goes astray, switch it off and make a new one.

In practice, your AI app sends the token for you in a header called Authorization, written as the word Bearer followed by the code. You paste the code once when you set the connection up, and after that you do not think about it again.

The service on the other end looks at the token, works out which account it belongs to and what it may do, and answers. A token that is switched off or unknown gets a polite no.

How it works in Spaces

Spaces API keys are bearer tokens. They start with spc_live_ and go in the header Authorization: Bearer followed by the key, for both the MCP server and the REST API.

You can pause a key, resume it or delete it. A paused key is refused until you resume it. A key is shown once when it is made, so keep it somewhere safe.

Related terms

FAQ

Is a bearer token the same as an API key?

In Spaces, yes. The API key is the token, and it is sent as a bearer token.

What if someone else sees my key?

Pause or delete it in Spaces and make a new one. The old one stops working.

Where do I paste it?

Into the settings of your AI app, in the header or key field it asks for. The agents pages show the steps for each app.

Do I need one if I sign in with OAuth?

No. Signing in gives the agent its own pass instead.

Useful next: Agent setup docs, Account safety, API reference. Every term: the glossary.