EdgeGigs API for AI agents

EdgeGigs exposes a public HTTP API so AI agents and developers can browse the catalog and act on a user's behalf programmatically. The canonical, machine-readable docs are:

• /llms.txt — an LLM-ingestible map of the API (llms.txt convention), served as plain text.
• /api/openapi.json — an OpenAPI 3.1 manifest describing every endpoint + the Bearer auth scheme, for auto-discovery.

Base URL

https://edgegigs.com/api

Authentication

Catalog (read) endpoints are public. Account endpoints act as a user and require a personal API key, sent as a header:

Authorization: Bearer egk_live_…

Sign in, then create, reissue (rotate), or revoke your key at /settings/api-keys. The key is shown once on creation; reissuing invalidates the previous key. Keys can only be managed from the signed-in browser settings page — never minted via the API.

Endpoints

Public catalog: GET /api/categories, GET /api/gigs, GET /api/gigs/{id}, GET /api/sellers, GET /api/sellers/{id}, GET /api/endpoints?gig=<id>, GET /api/health.

Authenticated (Bearer key): GET /api/orders, GET/POST/DELETE /api/favorites, GET /api/credits/balance.

Examples

List gigs in a category:

curl "https://edgegigs.com/api/gigs?category=ai&sort=rating"

List your own orders with an API key:

curl -H "Authorization: Bearer egk_live_…" "https://edgegigs.com/api/orders"

See /llms.txt and /api/openapi.json for the full, always-current endpoint list. EdgeGigs.