API Key Tester
Test any AI or API key in your browser — instantly see if it's valid, and why it isn't. Nothing is stored.
Test your Amazon SES credentials with the send email endpoint
Data verified 2026-07-13
Key format & how to get one
1. Visit https://console.aws.amazon.com/ses/ and sign in 2. Go to Account > API Keys & Tokens 3. Create new Access Key ID and Secret Access Key 4. Ensure sender email is verified in SES 5. Free tier: 62,000 emails/month (if using EC2)
Cannot test this key from your browser
This provider blocks in-browser requests or requires a server-side secret. Test it from a terminal instead:
curl -sS -X POST https://email.us-east-1.amazonaws.com/ -H 'Content-Type: application/x-www-form-urlencoded' -d 'Action=SendEmail&Source=test@example.com&Destination.ToAddresses.member.1=test@example.com&Message.Subject.Data=Test%20Email&Message.Subject.Charset=UTF-8&Message.Body.Text.Data=Hello%20world!&Message.Body.Text.Charset=UTF-8&Message.Body.Html.Data=<html><body><strong>Hello</strong>%20world!</body></html>&Message.Body.Html.Charset=UTF-8'
How it works
- Fast — the test is a direct call to the provider's own API endpoint, not a queue or a batch job. You get an answer in about a second.
- Private — your key is never sent to a trevorfox.com server. There is no backend here to send it to.
- Simple — pick a provider, paste the key, click test.
Pick a provider above and you'll get that provider's key format, where to generate a key, the exact endpoint the test calls, and a plain-language reading of whatever the API says back.
Where your key actually goes
This matters more than the usual "we don't store your data" line, so here is the specific mechanic.
For providers whose API allows browser requests, the test runs from your browser straight to the provider. The key goes to OpenAI, or Anthropic, or Stripe — the same place your own code would send it — and nowhere else. It is never transmitted to this site, never logged, and never stored. Close the tab and it's gone.
Not every API permits that. Roughly half of the providers here either block cross-origin browser requests or issue secret keys that should never be pasted into a web page at all. For those, the tool doesn't quietly proxy your key through a server — it gives you a curl command to run in your own terminal, with your key substituted in locally. Your key stays on your machine either way. The difference is only who makes the request: your browser, or your shell.
Each provider is labeled so you know which case you're in before you paste anything.
What the test actually proves
A green result means the provider accepted the key on that endpoint at that moment. That is narrower than "the key works for everything":
- A key can be valid but unfunded. Several AI providers return a perfectly good authentication result and then refuse actual inference calls because the account has no credit or an expired card.
- A key can be valid but scoped. Project-scoped and restricted keys authenticate fine while lacking permission for the specific model, endpoint, or resource you actually wanted.
- A key can be valid but rate-limited. A
429means the key is real — you're just being throttled.
So a pass rules out the most common failure (the key is wrong, revoked, or malformed). It does not promise that every downstream call will succeed.
Reading the common errors
Most key problems resolve to one of four responses, and the distinction between the first two is the one people most often get backwards:
| Status | Means | Usually because |
|---|---|---|
401 | Unauthorized — the key wasn't accepted | Wrong, revoked, expired, or malformed key; a stray space or a truncated copy/paste |
403 | Forbidden — the key is real but not allowed | Key lacks the scope/permission, or the account/region isn't entitled to that endpoint |
429 | Too many requests | The key is valid and being rate-limited or is out of quota |
200 | Accepted | The key authenticated on this endpoint |
If you're getting 401 on a key you just created, check for whitespace first. A trailing newline from a copy/paste is the single most common cause, and it's invisible.
Supported providers
Every provider has its own page with that provider's key format, where to generate a key, the endpoint the test calls, and the errors it returns. Key formats, endpoints, and the error dictionaries above are checked against each provider's live API and dated — not inferred from documentation that may have drifted.
AI (22)
- Anthropic Clauderuns in your browser
Test your Anthropic Claude API key with the messages endpoint
- AssemblyAIruns in your browser
Test your AssemblyAI API key with the transcript list endpoint
- Azure OpenAIruns in your browser
Test your Azure OpenAI resource key against your endpoint's models list (uses the api-key header, not Bearer)
- Cerebrasruns in your browser
Test your Cerebras Inference API key with the models endpoint
- Cohereruns in your browser
Test your Cohere API key with the generate endpoint
- Deepgramruns in your browser
Test your Deepgram API key with the projects endpoint
- DeepInfraruns in your browser
Test your DeepInfra API token with the OpenAI-compatible models endpoint
- DeepSeekruns in your browser
Test your DeepSeek API key with the chat completions endpoint
- ElevenLabsruns in your browser
Test your ElevenLabs API key with the user endpoint
- Fireworks AIruns in your browser
Test your Fireworks AI API key with the models endpoint
- Google Geminiruns in your browser
Test your Google Gemini API key with the generateContent endpoint
- Groqruns in your browser
Test your Groq API key with the chat completions endpoint
- Hugging Faceruns in your browser
Test your Hugging Face access token with the whoami endpoint
- Mistralruns in your browser
Test your Mistral API key with the models endpoint
- NVIDIA NIMruns in your browser
Test your NVIDIA API key (build.nvidia.com / integrate.api.nvidia.com) with a minimal chat request
- OpenAIruns in your browser
Test your OpenAI API key with the models endpoint
- OpenRouterruns in your browser
Test your OpenRouter API key with the key info endpoint
- Perplexityruns in your browser
Test your Perplexity (Sonar) API key with the chat completions endpoint
- Replicateruns in your browser
Test your Replicate API token with the account endpoint
- Stability AIruns in your browser
Test your Stability AI API key with the account endpoint
- Together AIruns in your browser
Test your Together AI API key with the models endpoint
- xAI Grokruns in your browser
Test your xAI Grok API key (api.x.ai) with the models endpoint. Note: xAI Grok is NOT the same as Groq — if you have a gsk_ key, use the Groq tester instead.
Data Enrichment (18)
- Clearbitruns in your terminal
Test your Clearbit API key with the company enrichment endpoint
- Coresignalruns in your terminal
Test your Coresignal API key with the companies endpoint
- Crunchbaseruns in your terminal
Test your Crunchbase API key with the organizations endpoint
- Data Axleruns in your terminal
Test your Data Axle API key with the business lookup endpoint
- Datanyzeruns in your terminal
Test your Datanyze API key with the companies endpoint
- Demandbaseruns in your terminal
Test your Demandbase API key with the accounts endpoint
- Enrichruns in your browser
Test your Enrich API key with the person enrichment endpoint
- FullContactruns in your terminal
Test your FullContact API key with the person enrichment endpoint
- HG Insightsruns in your terminal
Test your HG Insights API key with the companies endpoint
- LeadGeniusruns in your terminal
Test your LeadGenius API key with the companies endpoint
- Leadspaceruns in your terminal
Test your Leadspace API key with the contacts endpoint
- Lusharuns in your terminal
Test your Lusha API key with the contacts endpoint
- Mattermarkruns in your terminal
Test your Mattermark API key with the companies endpoint
- Melissaruns in your terminal
Test your Melissa API key with the address verification endpoint
- People Data Labsruns in your browser
Test your People Data Labs API key with the person enrichment endpoint
- Piplruns in your terminal
Test your Pipl API key with the search endpoint
- Snov.ioruns in your terminal
Test your Snov.io API key with the leads endpoint
- ZoomInforuns in your terminal
Test your ZoomInfo API key with the contacts endpoint
Email (9)
- Amazon SESruns in your terminal
Test your Amazon SES credentials with the send email endpoint
- Brevo (Sendinblue)runs in your browser
Test your Brevo API key with the send email endpoint
- Loopsruns in your terminal
Test your Loops API key with the contacts endpoint
- Mailgunruns in your terminal
Test your Mailgun API key with the messages endpoint
- Postmarkruns in your terminal
Test your Postmark Server Token with the email sending endpoint
- Resendruns in your browser
Test your Resend API key with the emails endpoint
- SendGridruns in your terminal
Test your SendGrid API key with the mail send endpoint
- SparkPostruns in your terminal
Test your SparkPost API key with the transmissions endpoint
- Twilioruns in your terminal
Test your Twilio Account SID and Auth Token with the messages endpoint
CRM (3)
Customer Support (3)
Payments (1)
- Striperuns in your terminal
Test your Stripe API key with the charges endpoint
FAQ
Is it safe to paste my API key here?
Your key is never sent to this site. For browser-testable providers the request goes directly from your browser to the provider's API; for everything else you get a curl command to run yourself and the key never leaves your machine. That said, the correct instinct is to distrust any site asking for a key — so treat a test key or a revocable key as the default habit, here and everywhere.
Why do some providers make me use the terminal instead?
Two reasons. Some APIs refuse cross-origin requests from a browser, so the call simply cannot be made from a web page. Others issue secret keys that are never meant to touch a browser at all — pasting one into any web page is a bad practice regardless of who wrote the page. In both cases the honest answer is a curl command rather than a server-side proxy that would require handing the key to someone else.
My key works here but fails in my app. Why?
Almost always scope, credit, or model access. This tests one specific endpoint. A key that authenticates against a /models listing can still be blocked from a particular model, out of credit, or missing a permission your app needs. Check the account's billing status and the key's restrictions.
Is xAI Grok the same as Groq?
No, and this trips people up constantly because the names are nearly identical. Groq (gsk_ keys, api.groq.com) is an inference hardware company. xAI Grok (api.x.ai) is Elon Musk's model. They are unrelated companies. If you have a gsk_ key, you want the Groq tester.
Does a passing test cost me anything?
For most providers, no. The majority of tests call a metadata endpoint — listing models, fetching account info — which is free and unmetered.
A handful of APIs offer no such endpoint, so the only way to authenticate is to actually use them. Those tests send a minimal Hello world! prompt capped at around 100 tokens: Anthropic, Google Gemini, Groq, DeepSeek, Cohere, Perplexity, and NVIDIA NIM. That's billed as a normal request, at a cost that rounds to a fraction of a cent, but it is not free and it will appear in your usage.
Related tools
Building with AI APIs? Elegant Atomics turns AI capability into B2B SaaS growth. Work with us →