Skavio USDC Payment Verification & Proof MCP

Audio transcribe

audio_transcribe

Idempotent

Transcribe a bounded source audio or video file supplied as base64 to text. Use for spoken media; not for OCR, invoice parsing, or PDF content conversion. This is a separately authenticated company Agent Tools relay; requires a valid Bearer API key, an enabled backend operation and an accepted payment mode. x402 returns a workload-specific quote and prepaid consumes shared company credits. Retry with the SAME idempotency_key and inputs to recover, not a new job. Admission is not delivery: poll skavio_agent_job_status, retrieve through skavio_agent_job_result, and verify SHA256. No anonymous execution.

Input Schema

Name	Required	Description	Default
`arguments`	Yes	Tool-specific structured input object. Supply the required named fields described by its JSON Schema; source bytes must respect encoded size limits. Never include wallet private keys, passwords or API tokens.
`payment_mode`	No	x402 returns a workload-specific quote; prepaid spends your existing shared company credits. No anonymous execution.	x402
`idempotency_key`	Yes	Stable job key; retry exactly the same inputs and payment mode with this key to recover safely.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / arguments / description

Added value: +"Tool-specific structured input object. Supply the required named fields described by its JSON Schema; source bytes must respect encoded size limits. Never include wallet private keys, passwords or API tokens."

Changed9 schema fields changedOct 17, 2026

changedInput schema / properties / arguments / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / arguments / properties

Added value: +{
+  "data_base64": {
+    "description": "Source document or audio bytes in base64, at most 3,000,000 encoded characters.",
+    "maxLength": 3000000,
+    "type": "string"
+  },
+  "units": {
+    "description": "Optional legacy count; verified against actual source bytes. Omit it for automatic measurement.",
+    "maximum": 30,
+    "minimum": 1,
+    "type": "integer"
+  }
+}

addedInput schema / properties / arguments / required
```
Added value: +[
+  "data_base64"
+]
```
removedInput schema / properties / arguments / title
```
Removed value: -"Arguments"
```

addedInput schema / properties / idempotency_key / description

Added value: +"Stable job key; retry exactly the same inputs and payment mode with this key to recover safely."

addedInput schema / properties / idempotency_key / maxLength
```
Added value: +128
```
addedInput schema / properties / idempotency_key / minLength
```
Added value: +8
```
addedInput schema / properties / idempotency_key / pattern
```
Added value: +"^[A-Za-z0-9_.:-]{8,128}$"
```

addedInput schema / properties / payment_mode / description

Added value: +"x402 returns a workload-specific quote; prepaid spends your existing shared company credits. No anonymous execution."

AddedOct 14, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare safe/idempotent/open-world hints; the description adds substantial undisclosed context: a separate Bearer-authenticated relay, an enabled backend operation, an accepted payment mode, x402 quote vs prepaid credit billing, and "no anonymous execution." It also correctly frames admission as asynchronous ("admission is not delivery"), which the annotations cannot convey. It stops short of stating rate limits, timeouts or cost magnitudes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose, exclusions and billing are front-loaded in the first three sentences, with the async polling workflow after. Information density is high and nearly every clause carries weight, though the auth/payment sentence packs four distinct constraints into one line and could be split for scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by explaining that the call only enqueues work and that results come from skavio_agent_job_result with SHA256 verification. Combined with the payment-mode and idempotency guidance, an agent has everything needed to call this correctly and recover from failure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents data_base64, units and payment_mode; the baseline would be 3. The description earns above baseline by explaining the semantic role of idempotency_key ("retry with the SAME idempotency_key and inputs, not a new job") and the operational difference between x402 and prepaid, which the enum alone does not make actionable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — transcribe a bounded base64 audio/video file to text — with the size constraint baked in. It also explicitly disclaims adjacent tasks (OCR, invoice parsing, PDF conversion), which separates it from siblings like document_ocr, invoice_extract and pdf_to_text without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both the positive case ("use for spoken media") and the negative cases ("not for OCR, invoice parsing, or PDF content conversion"), which map directly to sibling tools. It goes further by prescribing the recovery path (retry with the same idempotency_key) and the follow-up sequence (job_status, job_result, SHA256 verify).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Skavio USDC Payment Verification & Proof MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Audio transcribe

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources