verified-burst
An MCP tool that lets your agent buy verified inference at hard decisions and pay only if the answer is correct. At an irreversible/ambiguous/deadline fork, your agent escalates to fast silicon, samples best-of-N, runs the answers through a verifier, and pays a few tenths of a cent over x402 — charged only if it passes. Non-verified results cost nothing. Budget-capped, BYOK.
Install
pip install verified-burst
# or zero-install: uvx verified-burst (pipx run verified-burst)
Add to your MCP client
{
"mcpServers": {
"verified-burst": {
"command": "verified-burst",
"env": {
"BURST_BUYER_KEY": "0x<your Base wallet private key>",
"BURST_PROVIDER_KEY": "csk-<your Cerebras key>"
}
}
}
}
Fund the wallet with a little USDC on Base. BURST_PROVIDER_KEY is optional
(BYOK — your tokens, your rate limit). BURST_ENDPOINT overrides the host
(default https://solcleus.com/v1/burst).
The tool
buy_verified_burst(request, strategy="best_of_n", n=3, verifier="self_consistency", answer_key=None, model=None)
buy_verified_burst(
request="Is this clause enforceable? yes/no",
answer_key=["regex", "(yes|no)"]
)
Returns the verified answer + a receipt. You are charged only when the verifier passes. Spend is capped per wallet server-side, so autonomous purchases are safe.
How the money moves (no mystery)
- The endpoint answers an unpaid call with HTTP 402 + payment requirements.
- This client signs an x402 (EIP-3009) authorization with your wallet and retries.
- The host verifies the answer and settles on-chain only if it passed — your USDC moves directly to the provider; the host eats the gas. Self-hosted facilitator, no third party holding funds.
Service discovery: GET https://solcleus.com/.well-known/x402.
Metadata
Release files for verified-burst 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| verified_burst-1.0.0.tar.gz | 5.0 kB | Without provenance | Details for verified_burst-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| verified_burst-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for verified_burst-1.0.0-py3-none-any.whl |
Total release size: 11.2 kB
Release files / verified_burst-1.0.0.tar.gz
| Download URL | verified_burst-1.0.0.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba4fd37f6b969ac3ab83bbfe4d3bb54e3f7a661baebd5fbaf39b443e36324d3b
|
|
BLAKE2b-256 checksum How to use checksums |
0e566da60804e776a167cbe945b8b2b280c5109430bb0e83c9e003952c6169a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / verified_burst-1.0.0-py3-none-any.whl
| Download URL | verified_burst-1.0.0-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c45ea8b4e6e62d6a62dbc87ca30f347884cbfb77e46c0d65085558f0cb4fa071
|
|
BLAKE2b-256 checksum How to use checksums |
aa313a7df27e04dcc0ab6bf528dbfb87d930a288c2cb729e14b3b8145bc6428f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for verified-burst 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.