Reusable agents
Save instructions for repeatable research, analysis and engineering jobs. Test them in the console and call them by API.
Find a model or API, build a reusable agent and run it in a bounded sandbox. Keep the tools, execution trace and deliverables together.
Capabilities, agents and execution
3 min
// Median latency
1
// API key
6
// Agent templates
Linux
// Sandbox runtime
A connected set of building blocks. Browse the live catalog for supported inputs, limits and working examples.
Save instructions for repeatable research, analysis and engineering jobs. Test them in the console and call them by API.
Generate text through the connected model capability. The catalog identifies the supported model and the cost of each run.
Fetch public research, repository and package data through validated capability inputs. Results preserve the original source URLs.
Ask your agent to test its calculations or generated code. Inspect the actual command, exit code and output in the run trace.
Retrieve current public data when your task needs it. Provider responses are attached to the run instead of replaced with sample data.
One run reserves one credit. Failed and cancelled runs return it once. See your balance and run history in the workspace.
Name an agent and save its task instructions. Run it again with new context or update it when the job changes.
Give each agent run a fresh Linux sandbox with Node and Python. Collect the generated files before the environment stops.
Read the submitted input, tool trace, generated files and final status. Download the deliverables as an archive.
Start with a working pattern. Save the instructions, test a run and inspect what the agent actually did.
Turn a question into a brief with sources.
Connect language reasoning to public APIs, executable code and a filesystem. Keep the result grounded in the work your agent actually performed.
Use the supported language capability from the catalog.
Query public APIs with explicit, validated inputs.
Every sandbox run has a timeout and a clear end.
Inspect the evidence before relying on an output.
Connected capabilities for language, public research, repositories and packages. Browse the catalog for the actual inputs and limits.
Your input, the tools used, actual command output and the final result. Inspect the work before it becomes part of your workflow.
The submitted request
Tools and command results
Files and deliverables
Credits and model tokens
Build and test your agents in a visual workspace.
Get startedSubmit runs and retrieve results from your application.
Get startedConnect your local assistant through MCP.
Get startedBuild source-backed briefs from public data.
Explore agentsGenerate code, run checks and download files.
Explore agentsAnalyze small datasets and prepare reports.
Explore agentsCall capabilities and agents through an API.
Explore agentsDeployment model, ownership, evaluation and what happens on a bad day.
Your account and run records are stored in our managed database. Agent execution uses a hosted sandbox and connected model providers. Downloaded artifacts remain yours to use. Do not submit secrets or data you are not authorized to process.
Create an account and use your three starter credits. Choose a capability or describe a small task. A sandbox run has up to three minutes to complete; the workspace shows progress and the final result.
Yes. Create a revocable API key and follow the working requests in the documentation. You can submit a capability or agent run, inspect its status and retrieve its output from your application.
You can read and download the files generated by your runs. Review their contents and any dependency licenses before using them. Model and provider services remain subject to their own terms.
Each accepted run reserves one credit. Failed and cancelled runs return that credit once. Three starter credits are included. The six monthly plans list their credit allocations on the pricing page.
Inspect the trace and verify the result before relying on it. Agents can make mistakes. Narrow the task, add missing context and rerun when needed. A completed run is evidence of execution, not a guarantee that every conclusion is correct.
The live catalog identifies the models and APIs currently connected to Allfurdfr. Agent runs use the configured language model with sandbox tools. We do not list unsupported providers as available integrations.
Save your instructions as an agent and run it again with new context. Active subscribers can enable daily or weekly schedules. API access lets your own applications submit work and read its results.
Start with a concrete deliverable. Follow the tool trace, inspect the generated files and decide what to reuse from the result.
// Three free runs. No credit card required.