Live · about 1,300 discoverable · 1 runnable

Your agent spends real money.Never more than you declared.

sealyx is one API key over capabilities that would otherwise each need their own account, key and invoice. You declare a ceiling on every run, and sealyx reserves it before it contacts any vendor. If the vendor charges more than your ceiling, the overage is ours.

Give this to your agent

  • Fetches a URL
  • Runs a shell command
  • That is the whole requirement
curl -s https://sealyx.ai/SKILL.md

It reads the file and takes it from there.

You will still need a key. There is no public sign-up — the first one is issued out of band, and nothing on this page will ask you for a card.

One entrance

Everything is discoverable. One thing is runnable.

your agent

sealyx
  • web → markdownrunnable
  • search resultsdiscoverable
  • company datadiscoverable
  • people datadiscoverable
  • product datadiscoverable
  • enrichmentdiscoverable
  • data retrievaldiscoverable
  • …about 1,300 in all

discover and inspect reach about 1,300 capabilities across 23 providers, and every one of them carries a runnable flag so an agent can tell before it spends a call. run executes what a human has read the billing notes for. Today that is one capability, and the reason is worth reading.

Three verbs

Find it, learn how to call it, then spend.

  1. 01

    discover

    Natural language in, a short list of candidates out — an id, one line of why, and a price. It answers which one, and nothing more.

  2. 02

    inspect

    The full input schema, plus the prose rules a schema cannot hold. It is a separate verb because its payload is two orders of magnitude larger than a search result; folding it into discover would bury the answer under schema nobody asked for.

  3. 03

    run

    Executes and pays. The ceiling is reserved first, the dispatch is at-most-once, and nothing that spends money is ever retried automatically — the upstream has no idempotency of its own, so sealyx guarantees it from its own state.

A ceiling is a cap on what you can lose, not an estimate.

1,300
capabilities discover reaches, across 23 providers
1
capability run will execute today, admitted by a human reading the notes
0
automatic retries on anything that spends money, under any error

What a ceiling actually buys

Reserved before anyone is contacted

The ceiling is held against your account before sealyx calls a vendor — not reconciled afterwards. sealyx pays vendors with its own key, so settling after the fact would mean handing you a bill you never agreed to.

The overage is ours

If a vendor charges above your declared ceiling, you are charged your ceiling and sealyx absorbs the difference. That is what makes a ceiling a cap on what you can lose rather than an estimate you are on the hook for.

At-most-once, and never a silent retry

The upstream has no idempotency mechanism of its own: two identical posts are two runs and two charges. sealyx guarantees at-most-once dispatch entirely from its own state, and never automatically retries a spend — not on timeout, not on 5xx, not on a dropped connection.

Unknown stays unknown

When sealyx cannot tell whether a vendor ran your job, it keeps the hold and marks the run UNKNOWN instead of guessing. An over-held hold is visible and recoverable; a wrongly released one is money already gone. A sweeper closes open runs on evidence, not on a clock.

A real session

Three commands, and one that ends badly.

discover → inspect → run

$ sealyx discover -q "scrape a web page as markdown"
monid:context.dev/web/scrape/markdown
  Fetch a URL and return its main content as Markdown, with boilerplate removed.

1 result(s). Next: sealyx inspect <id>

$ sealyx inspect monid:context.dev/web/scrape/markdown
… input.queryParams.url (string, required) · price 900 micros · runnable

$ sealyx run monid:context.dev/web/scrape/markdown \
    --input '{"queryParams":{"url":"https://example.com"}}' \
    --max-cost '$0.005' -o page.json
ceiling $0.005000 (5000 micros) · idempotency-key 9f1c4e2a-…
output → page.json
{ "runId": "run_c59ff16a…", "status": "COMPLETED" }

charged $0.000900

the outcome nobody can rule out

$ sealyx run monid:context.dev/web/scrape/markdown …
error: the outcome of this run is unknown: upstream timed out
  The run may have executed. Do NOT re-run it plainly — retry
  with the same key:
    --idempotency-key cac887e8-…
  or check first: sealyx runs list

$ echo $?
75

A timeout does not prove the vendor did nothing. sealyx keeps the hold, marks the run UNKNOWN, and hands back the key that makes a retry replay the original run instead of buying a second one. An over-held hold is visible and recoverable; a wrongly released one is money we have already paid and cannot get back.

Surfaces

Three ways in.

  • SKILL.md

    One URL, and the agent learns the verbs, the ceiling rule, and the standing instruction to use the user's own tools before spending anything here.

    curl -s https://sealyx.ai/SKILL.md

  • The CLI

    sealyx covers discover, inspect, run, runs and keys, with zero runtime dependencies because an agent pays process startup three times per task. Not on a public registry yet.

    sealyx discover -q "scrape a page"

  • Plain HTTP

    A bearer key, an idempotency key, and JSON. Everything the CLI and the skill do goes through the same three endpoints, documented in the quickstart.

    POST https://sealyx.ai/v1/run

MCP is not one of them. It is not built, and nothing here pretends otherwise.

Give this to your agent

One line, and it takes it from there.

curl -s https://sealyx.ai/SKILL.md
Can I sign up?

No. There is no public sign-up, no waitlist form and no card capture anywhere on this site. Keys are issued out of band today. Once you hold one, you mint and revoke your own.

Why will run execute only one capability?

Because a person has to read the billing notes first. Some upstream capabilities provision things that bill every month until explicitly released, and they declare a price shape identical to a one-shot call — the only signal is prose in a notes field. Others bill per result, so one call can cost an unbounded multiple of its sticker price. Admitting capabilities by price shape would, on a long enough timeline, sign us up for a subscription on a caller's behalf. So the list is short and grows by reading.

What happens when sealyx cannot tell whether the vendor ran my job?

The hold stays and the run is marked UNKNOWN rather than guessed at. The CLI exits 75 and prints the idempotency key; re-running with that key replays the original run instead of starting a second one. A 402, a 429, a 5xx and a gateway error page all fail to prove the upstream did nothing, so none of them release the hold.

What if the vendor charges more than my ceiling?

You are billed your ceiling and the overage is ours. That is what makes the ceiling a cap rather than an estimate — set it from the price inspect reported, a little above, and it bounds your loss rather than predicting your spend.

Can I rotate my own keys?

Yes — create, list and revoke, including the key you are authenticating with right now. Needing a second working key in order to respond to a leak would be a bad day made worse. Revocation takes effect on the next request.

How does an open run get closed?

A background sweeper closes them, and it decides by evidence rather than by the clock. No vendor run id means no evidence the vendor accepted the work, so the charge is zero. A vendor run id past the hard deadline means it did accept the work, and the hold is charged — otherwise "cause a timeout" would be a free way to run a job.