Verified Burst
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X402_PAY_TO | No | Seller wallet address to receive USDC payments (required if using x402 in real mode). | |
| X402_NETWORK | No | Network for x402 payments (e.g., base-sepolia). | |
| CEREBRAS_MODEL | No | Cerebras model to use (e.g., gpt-oss-120b or zai-glm-4.7). Default is likely gpt-oss-120b. | |
| X402_USDC_ASSET | No | USDC contract address on the chosen network. | |
| CEREBRAS_API_KEY | Yes | Your Cerebras API key (BYOK). Required. | |
| X402_FACILITATOR_URL | No | x402 facilitator URL for real payment settlement. If omitted, payments run in SIM mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buy_verified_burstA | Buy a verified inference burst at a hard/irreversible/low-confidence decision. Escalates to fast silicon, samples best-of-N, gates the answer through a verifier, and charges (x402) ONLY if it passes. Returns the verified answer + a receipt. Budget-capped per agent. Use when getting it wrong is costly. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or ambiguity between tools. The tool's purpose is singular and clearly defined.
The single tool 'buy_verified_burst' follows a consistent verb_noun pattern that aligns with the server name and clearly conveys its action.
The server has only one tool, which feels minimal; however, for a very narrow, specific service, this count may be acceptable but is at the lower boundary of reasonable scope.
The tool 'buy_verified_burst' encapsulates the entire intended workflow (buy, escalate, verify, charge) for verified inference bursts, leaving no obvious gaps for its stated purpose.