Agent-native artifact storage
Infrastructure for agent artifacts. Store, retrieve, share, and manage lifecycle for AI-generated artifacts.
Overview
OutputLayer gives AI agents a place to store the artifacts they produce: reports, images, exports, and intermediate files.
Upload a file and receive an ID plus a structured agent_contract that tells the agent exactly what to do next —
without parsing error messages or inspecting HTTP status codes.
Every response carries next-action guidance: where to retrieve the file, whether it can be shared publicly, when it expires, and what to do if the upload failed.
Why OutputLayer
AI agents generate artifacts constantly: reports, images, datasets, analysis results, and intermediate files.
Traditional object storage like S3 can store these files, but it does not provide workflow context for agents.
OutputLayer adds an agent-native layer on top of storage:
OutputLayer is not just storage — it is infrastructure for agent-generated outputs.
Pricing
Every account starts with a free trial: 5 uploads and 250 MB of storage — no payment required. After that, 1 upload = 1 credit. Credits start at ~3.5¢ per upload. No subscriptions — pay only for what you use.
Persist generated outputs up to 25 MB and retrieve them by ID or public URL.
Credits never expire. Storage is pooled across your account.
Purchase via POST /v1/credits/checkout.
Quick Example
No SDKs. No framework lock-in. Just HTTP.
# 1. Register an API key (no auth required) curl -X POST https://api.outputlayer.dev/v1/keys/register \ -H "Content-Type: application/json" \ -d '{"email": "agent@example.com"}' # Response: { "apiKey": "ol_live_...", "accountId": "key_01JXXXXX" } # 2. Upload an artifact curl -X POST https://api.outputlayer.dev/v1/outputs \ -H "Authorization: Bearer ol_live_..." \ -H "Idempotency-Key: job-001-attempt-1" \ -F "mimeType=application/pdf" \ -F "label=report" \ -F "content=@report.pdf" # Response includes outputId, status, contentUrl, and agent_contract
agent_contract
Every OutputLayer response — success and error — includes an agent_contract field.
Agents read next_actions[recommended=true].action to determine the next step,
with no message parsing and no status code switching required.
Full schema: 11 action codes, 19 error codes, all field definitions → docs/agent-contract-schema.md
Get Started
Register a key, read the agent integration guide, or explore the full OpenAPI schema. All discovery endpoints are public and require no authentication.
Contact