idiotproof sandbox
GPU video editing for agents.
Instinct / Grokbot · Codex / Claude Code · Python server
Start
Create an API key · Estimate costs
pip install idiotproof
export IDEA_SECRET_KEY=your_key
Install FFmpeg and ffprobe for video inspection, splitting, and concatenation.
Interfaces and tool schemas may change.
The default API is https://dev.67idea.com/v1; override it with
IDEA_API_BASE_URL or Idea(base_url=...). Use a key for that environment.
Never print your key or upload tokens.
Discover tools before uploading or rendering:
import asyncio
from idiotproof import Idea
async def main():
async with Idea() as idea:
tools = await idea.get_tools()
print([tool["id"] for tool in tools])
# Inspect the chosen tool's current docstring and schema before calling it.
# Example, if present: print(tools.submit_bobbie_job.__doc__)
asyncio.run(main())
Run a workflow
- Create a workspace:
chat_id = await idea.create_chat(). Reuse this ID. - Upload:
upload = await idea.upload_file(chat_id, "clip.mp4"). Up to 600 frames returnsworkspace_uri; longer videos split automatically and return orderedpartsandworkspace_uris. Images are also supported. - Call a discovered tool using its current schema. Start with a representative preview: submit, read feedback, revise, and inspect before scaling out. Tool calls are not automatically retried.
- Publish the resulting workspace path:
published = await idea.media_publish(chat_id, output_path). - Preview through your environment: localhost HTML for local coding agents, the host's media channel for Instinct/Grokbot, or your authenticated app UI for a custom server. Follow the matching guide above. Treat signed URLs as transient credentials; keep them out of logs and ordinary chat.
- Save wanted results with
await idea.download_media(chat_id, output_path, "final.mp4"), ordownload_and_concat()for ordered parts. Server media expires.
For multiple assets, use upload_batch(); its nested results retain asset/part
order. For errors, inspect IdeaError.code, status_code, and request_id.
A 403 requires checking key permissions and environment before retrying.
Read locally when needed
- API reference: calls, return shapes, concurrency, downloads, and concatenation.
- Media guide: preview strategy, Bobbie pipelines, VLM grounding, and constraints. Read before processing media.
- Why idiotproof: motivation and use cases.
These files ship inside the package. Locate them with:
from pathlib import Path
import idiotproof
docs = Path(idiotproof.__file__).parent / "docs"
Metadata
Release files for idiotproof 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| idiotproof-0.5.1.tar.gz | 75.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| idiotproof-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 115.7 kB
Release files / idiotproof-0.5.1.tar.gz
| Download URL | idiotproof-0.5.1.tar.gz |
|---|---|
| Size | 75.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f5e23388a05058d6f24a1703424e809a27c9091a801f8809010c0cd4ed54f02a
|
|
BLAKE2b-256 checksum How to use checksums |
f680ca7493c1c2a9d5bd4c83030dcc74123db176a55a5b923daa5733a93598bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / idiotproof-0.5.1-py3-none-any.whl
| Download URL | idiotproof-0.5.1-py3-none-any.whl |
|---|---|
| Size | 40.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a1a055cdd69d90404640a6c3bafab663e49dc28ee8e6f4f27503786c5d1b20da
|
|
BLAKE2b-256 checksum How to use checksums |
46a7b2f8d0baf5f6f60d465967dc02cd19bc04eb7cf0836191ace61940c94822
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency log