System Status

Partial Availability

Last checked: 2026-05-30 18:05:03 UTC

40

Total Adapters

2

Free / Available

0

Pool Ready

38

BYOK Only

Available — no key needed
Pool ready — master key configured
BYOK required

Adapter Status

ToolRoute

Free
Metatoolroute

Auto Router

Free
Metaauto

Playwright

BYOK
Code & DevOpsplaywright

Pexels

BYOK
Image & Mediapexels

GitHub

BYOK
Code & DevOpsgithub

OpenAI

BYOK
AI & LLMopenai

Firecrawl

BYOK
Search & Webfirecrawl

Twilio

BYOK
SMStwilio

Deepgram

BYOK
Voice & Audiodeepgram

Claude

BYOK
AI & LLMclaude

Replicate

BYOK
AI & LLMreplicate

ElevenLabs

BYOK
Voice & Audioelevenlabs

Resend

BYOK
Emailresend

SendGrid

BYOK
Emailsendgrid

Stripe

BYOK
Businessstripe

Supabase

BYOK
Data & Analyticssupabase

Vapi

BYOK
Voice & Audiovapi

Sentry

BYOK
Code & DevOpssentry

Calendar

BYOK
Productivitycalendar

Drive

BYOK
Productivitydrive

DeepL

BYOK
Contenttranslate

Mux

BYOK
Videomux

Unsplash

BYOK
Image & Mediaunsplash

Image Gen

BYOK
Image & Mediaimage

Web Search

BYOK
Search & Websearch

Shotstack

BYOK
Videoshotstack

HeyGen

BYOK
Videoheygen

Postiz

BYOK
Social & Outreachpostiz

Context7

BYOK
AI & LLMcontext7

Whisper

BYOK
Voice & Audiowhisper

Screenshot

BYOK
Code & DevOpsscreenshot

PDF Tools

BYOK
Contentpdf

Remove.bg

BYOK
Image & Mediaremovebg

Creatify

BYOK
Videocreatify

Apollo

BYOK
Social & Outreachapollo

Shippo

BYOK
Businessshippo

Outscraper

BYOK
Data & Analyticsoutscraper

Textbelt

BYOK
SMStextbelt

DataForSEO

BYOK
Data & Analyticsdataforseo

Creatomate

BYOK
Videocreatomate

Pool adapters use ToolRoute-managed API keys. Requests are billed through your ToolRoute credits at a zero-markup pass-through rate.

BYOK (Bring Your Own Key) adapters require you to configure your own API key via the dashboard. ToolRoute handles routing and billing but uses your key for the upstream call.

Free adapters require no API key and have no per-call cost beyond your plan rate limits.

This page auto-refreshes every 30 seconds. Adapter availability reflects key configuration status, not real-time upstream provider health.