API marketplace · workers · MCP

Run catalog workers from one API

For backend and platform teams who need ready-made jobs—not another pile of glue code. POST a JSON payload, get a job_uuid, poll for structured results—often in under ten lines in Node or Python.

Get your free API key Read the docs
  • No credit card to start
  • Free credits on signup
  • Cancel anytime 
# Queue a job (returns job_uuid immediately)
curl -X POST https://api.seek-api.com/v1/workers/img-to-pdf/jobs \
  -H "x-api-key: •••••••••••••••••••••••" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://i.co/img.png"}'

# Poll until SUCCEEDED, then read output
curl https://api.seek-api.com/v1/jobs/j_8f3ka2n \
  -H "x-api-key: •••••••••••••••••••••••"

Response is JSON with job_uuid and status; poll /v1/jobs/{uuid} until SUCCEEDED, then read output (typical round-trip under a few seconds for small inputs).

Stop rebuilding
what you could call over HTTP

Seek-api is for teams who want catalog workers and predictable jobs—not another queue to babysit.

  • Boilerplate that is not your product

    Every team ends up maintaining PDF pipelines, media transforms, and enrichment glue that customers never see—until it breaks.

  • Agents stuck in chat-only mode

    LLMs are only as capable as the tools they can call. Without stable, callable workers, agents cannot complete real work in your systems.

  • Operational drag on small teams

    Provisioning, scaling, and monitoring bespoke workers pulls engineers away from roadmap work, especially when demand is spiky.

How it works

Three steps. Same flow from curl, SDKs, or MCP-connected agents.

  1. Choose a worker

    Browse the catalogue or wire MCP tools so your agent can call the same workers your backend uses.

  2. POST with your API key

    Send JSON to the worker endpoint. You get a job UUID immediately—no long-lived connections required.

  3. Fetch the result

    Poll the job endpoint until completion, then read structured JSON (and any artifacts) for your pipeline or UI.

Built for production.
Made for developers.

Each capability below maps to a concrete outcome: less glue code, clearer billing, agents that can act.

Worker catalogue

Pick from a growing set of ready-made workers so your roadmap stays focused on product features instead of bespoke pipelines.

Simple HTTP API

POST JSON with your API key so any service or script can enqueue work without adopting a heavy framework first.

Async job queue

Receive a job UUID immediately so your UI and backends stay responsive while work finishes in the background.

Pay-as-you-go

Metered billing per run or per event so cost tracks usage instead of paying for idle capacity you do not need.

MCP for AI agents

Wire catalogue workers into MCP so agents invoke the same tools as your servers, with structured inputs and outputs.

Zero infrastructure

We manage the queues, the runtimes, and the scaling. You just send payloads and get results, without ever writing a Dockerfile or configuring a worker node.

Works with your stack

  • HTTP / REST
  • Node.js
  • Python
  • curl
  • MCP

Where teams use Seek-api

Common patterns for adopting catalogue workers without rewriting your existing backend.

01

Product integrations

Ship image, audio, and document workflows behind your API without owning encoders, storage glue, or retry logic end to end.

02

AI agents that do real work

Give agents MCP access to catalogue workers so they can fetch data, transform files, and post results—not only stream text.

03

Internal platforms

Let squads share metered workers across services: one catalogue, one billing model, consistent job semantics.

04

Vendor-free pipelines

Skip integrating five different SaaS tools for common jobs. Seek-api centralizes standard workflows under a single API and billing dashboard.

Pricing you can reason about

Simple utility pricing models designed for production workloads.

No monthly fee

Pay-as-you-go

Free to start

Deposit funds into your balance. Only pay for completed runs—per execution or per result, depending on the worker.

  • Pay only for completed work
  • $3 free credits on signup (valid 30 days)
  • Top up your balance anytime
  • 10 concurrent jobs
  • No credit card required
Get started free
Popular

Pro

$9.99 /month

Everything in Pay-as-you-go, plus higher concurrency limits for teams that need more parallel throughput.

  • Everything in Pay-as-you-go
  • 30 concurrent jobs
  • Priority scaling
  • Cancel anytime
Subscribe to Pro

Enterprise contracts and volume discounts: staff@seek-api.com

Frequently asked questions

How does pricing work?
Two plans: Pay-as-you-go (no monthly fee, pay per completed run) with $3 free credits on signup, and Pro at $9.99/month for higher concurrency (30 concurrent jobs vs 10). You are only billed for completed work, never idle time.
Do you train on my data?
Seek-api runs your jobs and stores the outputs needed for billing and support. Read the data processing terms in the docs and privacy policy for retention and subprocessors.
How do I connect workers to my AI agent?
Use the Model Context Protocol (MCP) to expose catalogue workers as tools. The same worker can be called from your backend over HTTP and from an agent through MCP with consistent semantics.
What happens if I exceed rate limits?
Requests may be throttled with standard HTTP status codes. The docs describe default limits and how to request higher throughput for production workloads.
Which regions are supported?
Check the documentation for current regions and latency guidance. Enterprise plans can discuss data residency requirements with the team.
Is there a free tier?
Yes—signup includes free credits so you can integrate and run test jobs before spending.
Ready when you are

Get your API key and run a job today

Same signup flow as the hero: free credits, no card required. Use the docs to go from curl to production traffic.

Get your free API key Explore the docs

No credit card required · Free credits on signup · Cancel anytime