OAuth
Bring channels online once
OAuth
Bring channels online once
Connect LinkedIn, X, Instagram and Facebook through Rabt instead of maintaining four developer apps.
linkedinxmeta
IncludedView
Connected toolsfor a more intelligent world
Build automation that publishes everywhere.
ChatGPT, Claude, and your own tools publish through rabt.dev with one API, connected accounts, and honest per-network status.
Live routing map
Agents to social platforms
rabt.dev
G
ChatGPT
content agent
C
Claude
strategy agent
connected
X
connected
connected
2
AI agents
1
publish API
3
live channels
OAuth healthy
Brief
Agent drafts a post
Your workflow produces text, hashtags and optional media.
Route
Rabt fans it out
One request becomes platform-safe payloads for each channel.
Ledger
Every result is logged
Successes, partial failures and post IDs stay inspectable.
API ledger
One request. Platform-aware delivery.
Rabt keeps the request shape boring on purpose. The complexity sits behind the endpoint, where channel tokens, media rules and publish outcomes can be handled consistently.
publish.sh
POST /api/v1/publishcurl -X POST https://rabt.dev/api/v1/publish \
-H "Authorization: Bearer rabt_live_xxx" \
-H "Content-Type: application/json" \
-d '{
"providers": ["twitter", "linkedin", "instagram"],
"text": "Launch notes drafted by my agent.",
"media_urls": ["https://cdn.example.com/launch-card.png"]
}'Agent tools
The boring infrastructure agents need before they post.
Keys, OAuth, routing and logs are treated as first-class product surfaces, not glue code hidden in a demo.
Keys
Issue scoped agent keys
Keys
Issue scoped agent keys
Create revocable API keys for each product, workflow or customer-facing automation.
bearerserverrotate
IncludedView
Safety
Keep tokens off your stack
Safety
Keep tokens off your stack
Platform tokens are encrypted, redacted and refreshed behind the API boundary.
encryptedredactedrefresh
IncludedView
Fan out
One shape for every publish
Fan out
One shape for every publish
Send text and media once. Rabt adapts channel requirements and returns per-network status.
json207status
IncludedView
API
Built for agent runtimes
API
Built for agent runtimes
Simple REST calls make Rabt easy to wire into tools, jobs, MCP servers and internal copilots.
restmcpjobs
IncludedView
Ops
Trace channel health
Ops
Trace channel health
Use logs and connection state to debug rate limits, permissions and partial publishes fast.
logshealthaudit
IncludedView
Channels
Four networks behind one small interface.
Connect the accounts your agent is allowed to use, then let Rabt return explicit status for every destination in the request.
Profiles and organization targets.
X
Text-first updates from agents and apps.
Feed publishing with public media URLs.
Page publishing for multi-channel launches.
Pricing
Start with one agent. Scale when it is posting real work.
The plan shape stays simple: connected accounts, API keys, publish volume and support.
Starter
For testing an agent or a side project.
$0/mo
- 2 connected accounts
- 1 API key
- 100 publishes / month
- Publish logs
Pro
PopularFor production agent workflows.
$29/mo
- 10 connected accounts
- Unlimited API keys
- 5,000 publishes / month
- 60 requests / minute
- Email support
Scale
For platforms and teams.
$99/mo
- Unlimited accounts
- Higher rate limits
- Multi-tenant keys
- Priority support
FAQ
The practical bits before you wire it in.
Short answers for teams adding social publishing to an agent workflow.
Ready for the first publish