For developers

One endpoint. A catalog your agent can call.

Eden Engine is a single HTTP MCP endpoint with a bearer token. Your agent searches the catalog, reads the price, runs the tool and pays from one balance. This is the technical side of the site. Looking for the plain version? Start on the home page.

MCP endpoint

https://mcp.eden-engine.com/mcp

Send your access key as Authorization: Bearer. No SDK, no OAuth flow. Create a key in the dashboard after you sign up; the quickstart walks through it.

Get your client config Read the docs

Build with it

Install configPick your client, hand it SKILL.md, and it writes its own config. No account needed to install.
DocsEndpoint, bearer token, config snippets for 7 clients, error codes and limits.
Tool catalog and schemasOne page per tool: input schema, price range, usage notes and a ready-to-paste call.

Understand it

The tool loopSearch, inspect, learn, run, settle: the five steps every call follows, with real requests.
What MCP isThe standard your assistant uses to talk to the endpoint, in plain terms.
Design decisionsThe six choices that keep an AI with a balance safe, with the technical detail underneath.
Versus a plain API proxyManual or guess, priced before or billed after: the differences that only show once an agent is making calls.

Check on it

StatusWhether the site, the API and the tool catalog are answering right now.

Sending this to someone who does not code? These pages say the same things in plain words: how it works, why Eden Engine, how it compares and what MCP is.