Speko
Inspect your Speko voice-AI account from Claude — agents, calls, transcripts, recordings, phone numbers, credits and usage — plus speech-to-text transcription.
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Speko runs voice AI agents that make and take phone calls. This connector gives Claude read access to that account, plus one audio capability: transcription. Ask it to list your agents and their versions, pull a call transcript or recording, check which phone numbers you hold, inspect a knowledge base, or review credit balance and usage. Give it an audio file or a recording URL and it returns text. It can also search the Speko documentation and turn an existing voice-agent config into a Speko draft. Creating agents, deploying them, placing calls and generating speech are not available through this connector, and no request can enable them. Those live in the Speko dashboard, the REST API and the SDKs.
- Integration type
- Connector
- Verification status
Verified connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-08-15
- Tool count
- 59
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Your Claude Discoverability Score is being prepared
Claude can surface a verified Connector when it matches a user’s Prompt.We are preparing Speko’s Discoverability Score and will publish it when the benchmark is ready.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
About Claude's Discoverability Score
Your Connector now competes to appear for users’ prompts
Competitive lineup
59 tools agents can invoke
How do I improve a Verified connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.
