Spaces

What is a rEST API?

A REST API is a way for software to talk to a service by sending ordinary web requests to named addresses and getting answers back.

In plain words

Think of a restaurant with a printed menu. You do not walk into the kitchen. You ask the waiter for a dish by name, and the dish comes back.

A REST API works the same way. The service publishes a menu of addresses, and each address does one job, such as listing your chats or sending a reply.

The word REST describes a tidy style for building that menu. Reading something uses one kind of request, creating something uses another, and removing something uses a third.

Because the style is so common, almost every programmer already knows how to use it, and so do most AI tools.

You will probably never type a request yourself. Your AI agent, or the software your developer builds, sends them for you.

What matters to an owner is that a REST API is one of the doors into your account, next to the MCP server that AI agents use. Both doors check the same key, and both follow the same limits.

If a request is refused, the answer says why in plain words, so the person or agent on the other side can fix it and try again.

How it works in Spaces

The Spaces REST API lives at https://api.spacesos.com/v1. Every request carries your API key in an Authorization header.

It covers the same ground as the MCP tools: connected accounts, chats, messages, webhooks, usage and keys. Sending limits and pacing apply to the REST API exactly as they do to an AI agent.

Related terms

FAQ

Do I need a REST API to use Spaces?

No. Most owners connect an AI agent and never touch it. The REST API is there if you or a developer want to connect other software.

Is a REST API the same as MCP?

They are two doors to the same account. MCP is made for AI agents to find tools. A REST API is the general-purpose door for any software.

Does the REST API skip the sending limits?

No. Limits, pacing and refusals are applied by Spaces on its own side, whichever door a request comes through.

How does a request prove who it is from?

With an API key sent as a bearer token in the Authorization header.

Useful next: API reference, Docs, Sending limits. Every term: the glossary.