For AI Agents

The gas station for the
machine economy.

When your agent needs a blog post, a SWOT, a receipt parsed, a pitch deck drafted, it shouldn't have to wake up a human to get it. Hire sells scoped units of digital labor at flat per-job prices. Perfect fuel for an agentic stack.

Why Hire is built for agents

Flat per-job pricing. No subscription.

Your agent pays for outcomes, not seats. Every job has one price, no tokens to count, no tier to negotiate. The unit economics work at a single transaction.

Deterministic, scoped catalog.

No hallucinated capabilities. The catalog is the entire menu. What your agent hires is what it gets, every time, shaped the same way.

No session state. No memory.

Every job is an atomic transaction. Perfect for ephemeral agents that spin up, complete a task, and die. The amnesia is the feature. Your agent isn't fighting context accumulation.

Crypto-native payments. x402-ready.

Card, ACH, or crypto. Every checkout is a discrete payable unit. When agent-to-agent micropayments arrive, the plumbing already knows how to accept them.

“The dawn of a massivemachine-to-machine gig economy.”

Every agent will need to pay other agents for work that falls outside its specialty. The infrastructure to do that at the speed of a single HTTP request doesn't exist yet. Except as a vending machine.

API Reference

v1 Draft. Endpoint coming Q2 2026

This is the shape. The endpoints below are not live yet: we're publishing the contract so integrators can design against it now and flip the switch when the billing plumbing catches up. Every element of this schema is already modeled in the production database and Stripe account.

Authentication

Per-agent API key, passed as a Bearer token in the Authorization header. Billing runs against a single Stripe customer tied to your account. Rate limits, budget caps, and usage logs live there.

POST /api/v1/jobs

Create a job. Hire validates the job_id against the catalog, charges the card on file, and starts processing. Returns 202 with anorder_id to poll.

Request
POST /api/v1/jobs
Authorization: Bearer hnn_key_abc123...
Content-Type: application/json

{
  "job_id": "grant-proposal",
  "stripe_price_id": "price_1T6YExDziywAg0f6QpzA3n5m",
  "input_text": "Our nonprofit serves youth literacy in rural counties. We're applying to the Walton Family Foundation for a 2-year $250K capacity grant...",
  "input_files": [],
  "idempotency_key": "agent-pipeline-run-9f3e-2026-04-20"
}
Response 202 Accepted
HTTP/1.1 202 Accepted
Content-Type: application/json

{
  "order_id": "d35c5059-3a75-49e1-85fd-efd6f3c5a41b",
  "status": "processing",
  "job_id": "grant-proposal",
  "amount_usd": 99.99,
  "complexity_tier": 3,
  "estimated_completion_seconds": 90,
  "poll_url": "/api/v1/jobs/d35c5059-3a75-49e1-85fd-efd6f3c5a41b"
}

stripe_price_id is optional. Hire maintains a 1:1 map between the 76 catalog jobs and live Stripe price IDs. Supply it explicitly to bypass catalog lookup, or omit and Hire resolves it fromjob_id.

GET /api/v1/jobs/:order_id

Poll until status iscompleted orfailed. Tier 1 jobs typically complete in under 15 seconds; tier 3 jobs in under 120. Reasonable poll interval: 3 seconds.

Response 200 OK (completed)
HTTP/1.1 200 OK
Content-Type: application/json

{
  "order_id": "d35c5059-3a75-49e1-85fd-efd6f3c5a41b",
  "status": "completed",
  "job_id": "grant-proposal",
  "complexity_tier": 3,
  "amount_usd": 99.99,
  "result_text": "EXECUTIVE SUMMARY\n\nThe [Organization Name] Youth Literacy...",
  "result_files": [],
  "created_at": "2026-04-20T18:12:03Z",
  "completed_at": "2026-04-20T18:13:27Z",

  "data_retained": null,
  "files_deleted_at": "2026-04-20T18:13:27Z",
  "input_text_hash_sha256": "a3f5c19b2e8d4f6...",
  "receipt_url": "/receipts/d35c5059-3a75-49e1-85fd-efd6f3c5a41b"
}

The amnesia receipt

Every completed job response carries four fields that prove we kept nothing:

  • data_retained: nullExplicit null, not an empty object. Marketing says “we delete files”; this is the contract.
  • files_deleted_atISO-8601 timestamp of deletion. Usually equal to completed_at.
  • input_text_hash_sha256Proves what you sent without retaining it. You can verify the hash against your local copy.
  • receipt_urlA signed URL your auditor or compliance team can hit to confirm the transaction. Only transaction metadata, never content.

Privacy isn't a checkbox. It's the architecture. The response schema is where the architecture becomes legible to the agent calling us.

Error shape

All errors return a stable JSON envelope. Agents can pattern-match onerror.codewithout parsing prose.

Error envelope
{
  "error": {
    "code": "job_not_in_catalog" | "insufficient_funds" | "content_moderation_blocked"
          | "input_validation_failed" | "rate_limited" | "server_error",
    "message": "Human-readable explanation",
    "retryable": boolean
  }
}

Shapes of agentic demand

Agents hiring out subtasks

Your agent is mid-pipeline and needs a blog post, a SWOT, a receipt parsed. Call the catalog, pay the price, get the artifact, keep moving.

Agent marketplaces

Agents that broker other agents' work. Hire becomes a settleable, priced capability in a larger graph. No negotiation, no context hand-off.

Crypto-native AI services

Protocol-level AI commerce. Agent sends payment, Hire returns the artifact. The transaction is the interface.

The catalog is already agent-readable. The API schema above is the live spec. Endpoints flip on in Q2 2026. Building an agent that needs scoped labor? Start a conversation and we'll route you into the early-access list.

Email [email protected]See the catalog
RADIO