resources / api docs

Registry API

Mint a key on your dashboard, send it as a bearer token, and read the registry or execute a skill's tool from your own agent stack.

Authentication

Keys are shown once at creation and stored only as a hash. Send them in the Authorization header; unauthenticated reads are allowed on public listings but are rate limited.

Authorization: Bearer ems_live_xxxxxxxxxxxxxxxxxxxx

List skills

GET /api/public/skills?technique=cryo-EM&kind=MCP%20server

{
  "skills": [
    { "slug": "cryo2d-classify", "name": "Cryo 2D Classify",
      "technique": "cryo-EM", "toolCall": "cryo2d.classify",
      "version": "1.4.2", "verifiedBadge": "verified" }
  ]
}

Run a skill tool

Each call is metered and appears on your dashboard within seconds, with status, duration and any error returned by the MCP server.

POST /api/public/run
{ "slug": "cryo2d-classify",
  "args": { "stackUrl": "https://…/stack.mrc", "classes": 50 } }

{ "ok": true, "mode": "live", "durationMs": 1840,
  "output": { "classes": 50, "resolution": "6.2 A" } }

Errors

401 invalid or revoked key · 429 rate limited · 404 unknown slug · 502 the upstream MCP server failed. Failed runs are logged for diagnostics.