# RCS agents Sending RCS through the A2P Messaging API is coming soon. This page explains what you can do today: register your RCS agent in the A2P Messaging API project, country by country, so it is approved by the time sending is available. **Language:** en **Audience:** developer **TLDR:** Sending RCS through the A2P Messaging API is coming soon: there is no RCS endpoint yet. You can already register your RCS agent from the dashboard (Channels > RCS > Senders in the A2P Messaging API project), so it is approved when sending arrives. Each agent needs a registration per country, and a country without one is blocked: RCS has no wildcard route. An agent is tied to one provider. The registration process is the same as on the platform. **Search keywords:** rcs, rcs api, send rcs, rcs agent, rcs sender, register rcs agent, rcs registration, rcs countries, rich communication services, branded messaging, verified sender, coming soon **Related pages:** /platform/en/channels/rcs/senders-verification, /platform/en/channels/rcs/availability, /a2p-messaging-api/channels/sms/wildcard-route **Docs index (every page):** https://staging-instasent-docs-nextjs.oscar-284.workers.dev/llms.txt **This zone's index:** https://staging-instasent-docs-nextjs.oscar-284.workers.dev/a2p-messaging-api/llms-full.txt **This page:** https://staging-instasent-docs-nextjs.oscar-284.workers.dev/a2p-messaging-api/channels/rcs/agents/ (HTML) · https://staging-instasent-docs-nextjs.oscar-284.workers.dev/a2p-messaging-api/channels/rcs/agents.md (Markdown) **RCS** is messaging that arrives in the phone's default messaging app with your verified brand up front — name, logo and colour — instead of a bare sender name. On RCS the sender is an **agent**: the brand identity you register, and that the operators approve, before anything is sent. > **Note**: **Sending RCS through the A2P Messaging API is coming soon.** There is no RCS endpoint yet, > and the request format is not published. Today the API sends SMS. ## Register your agent now Approving an RCS agent takes time — operators and the network review it country by country — so you don't have to wait for the endpoint to start. You can already **create your agent and register it** in your A2P Messaging API project, and have it approved by the time sending through the API is available. In the dashboard, the A2P Messaging API project has the RCS channel under **Channels > RCS**, and the agents are in its **Senders** tab. The RCS channel has no **Settings** tab: everything about the agent is done from the agent itself. The registration is the **same process as on the platform**: create the sender, register it for each country, complete the organization and compliance data, and follow each register's status until it is active. The one difference: an A2P Messaging API project has **no default RCS sender**, because each API call names its sender. The process is documented once: - [RCS senders & verification](/platform/en/channels/rcs/senders-verification) - The full registration process, step by step, with every status. - [Your RCS agent profile](/platform/en/channels/rcs/agent-profile) - Every field your contacts will see, with the live previews. - [RCS agent best practices](/platform/en/channels/rcs/agent-best-practices) - How to design an agent that gets approved the first time. - [RCS acceptable use](/platform/en/channels/rcs/acceptable-use) - What an RCS agent can and can't send. ## Coverage As on [SMS](/a2p-messaging-api/channels/sms/coverage), **coverage** is where Instasent can deliver and on what conditions, and the countries and what each one asks for are documented once, in the countries catalog: - [RCS countries & availability](/platform/en/channels/rcs/availability) - The countries where RCS is available. - [Countries](/platform/en/channels/countries) - Every destination, with what it asks for on SMS and RCS. The same catalog is published as JSON: [`country-requirements.json`](https://staging-instasent-docs-nextjs.oscar-284.workers.dev/data/country-requirements.json), where each country states whether RCS is available there. The countries you can register your agent in are the ones the dashboard offers when you register it. What each country asks of your agent differs from SMS in one way: **on RCS there is always a registration**. The agent is registered **per country**, each registration is approved separately, and a country where your agent has no approved registration is a country you can't send RCS to — not registering is what blocks it. There is no best-effort delivery for an unregistered agent, and no list of destination countries to set: the agent's registrations *are* where it can send. The agent's registrations, and the status of each, are followed from the agent in the RCS channel's **Senders** tab — see [RCS senders & verification](/platform/en/channels/rcs/senders-verification). ## No wildcard route on RCS RCS has no equivalent of the SMS [wildcard route](/a2p-messaging-api/channels/sms/wildcard-route), and there won't be one. An RCS agent is always **tied to one provider**, so there is no sender without an identity for traffic to travel under: the agent has to be registered for each country before anything is sent there. --- This is one page of the Instasent documentation. For the complete machine-readable index of every guide and API reference, fetch https://staging-instasent-docs-nextjs.oscar-284.workers.dev/llms.txt — start there for full context.