Speech-to-Text APIDirect API access through SkillBoss

Speech to Text API

Speech to Text: Speech-to-text model for transcribing audio into text.

Modelstt
Pricing$0.08/1M tokens
AuthBearer YOUR_API_KEY
Paymentsx402 + MPP

Interface

Endpoint: POST https://api.skillboss.co/v1/run · Model: stt

Standard API flow

cURL interface

Use cURL when you want the clearest raw HTTP example. This is the fastest way to validate auth, inputs, output shape, and the canonical endpoint before wiring the API into code or agent workflows.

cURL
curl -X POST https://api.skillboss.co/v1/run \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "stt",
    "inputs": {
      // Your parameters here
    }
  }'

Best-Fit Use Cases

3 workflows
01

Call Speech to Text through one stable API surface

02

Ship integrations faster without vendor account setup

03

Use the capability directly inside human and agent workflows

Frequently Asked Questions

Docs · Browse all APIs

What is the Speech to Text API used for?

Speech to Text is a speech-to-text api available through SkillBoss. Teams use it to add Speech to Text to apps, automations, and AI agent workflows without managing separate vendor credentials. This page gives both humans and agents one stable place to understand the capability, pricing path, and invocation pattern before they ship it into production.

How do I call Speech to Text on SkillBoss?

Send a POST request to https://api.skillboss.co/v1/run with "model": "stt" and an "inputs" object. SkillBoss handles auth, billing, and the unified API layer. If you are testing the endpoint manually, start with the cURL or Python tab below. If you are wiring an autonomous agent, use the x402 or MPP tabs when the payment path matters.

Why use SkillBoss instead of the native minimax setup?

SkillBoss gives you one API key, pay-as-you-go billing, and a consistent integration flow across many APIs. That reduces setup time and makes the endpoint easier to use in Claude Code, Cursor, Windsurf, and other agents. It also gives you a canonical public page, consistent docs, and one billing surface instead of forcing each team to juggle provider-specific auth and pricing rules.

Is Speech to Text good for AI agents as well as human developers?

Yes. This page is designed as a discovery surface for both humans and agents: clear capability framing, direct code examples, and a stable canonical URL make it easier to find, evaluate, and invoke. The structure is deliberate so search engines, agent runtimes, and developers can all understand what the endpoint does, how it is paid for, and which next pages matter.

Does Speech to Text support x402 or MPP machine payments?

Speech to Text is better served through the standard SkillBoss API key flow. x402 and MPP work best when pricing is deterministic before execution, which is not the safest assumption for this endpoint.

One API key. 100+ models.

Start using Speech to Text now

Call stt through SkillBoss — same endpoint, zero markup.