DEVELOPER PLATFORM

Give every AI agent
the same approved answer.

Publish current pricing, product facts, proof, and customer actions once. Make them available through your website, REST API, and MCP server.

See the object ↓Request developer access ↗

decision-graph-v1READY

{
  "decision": "Will this work with our stack?",
  "fit": "verified",
  "evidence": ["integration", "security", "rollout"],
  "next_action": "review_rollout",
  "authority": "approved"
}

ONE APPROVED SOURCE

Update once.
Keep every answer current.

Your website, API, and MCP read the same product facts, supporting proof, and approved next action.

DECISION GRAPHrevision 14one canonical buying state

WEBSITEREST APIMCPAGENT FILESCRM RECEIPT

CHOOSE YOUR SURFACE

REST API

Put the decision inside your product.

Read the current replay, inspect evidence, claim an artifact, and submit approved operations through stable endpoints.

GET /api/v2/buyer-sites/:id

MCP SERVER

Let agents use Eli as a tool.

Expose the same read and controlled-write operations inside agent workflows without creating a second product state.

tools: build · get · approve · publish

AGENT DISCOVERY

Make approved facts easy to find.

Publish agent-readable company facts, capabilities, and allowed actions from the same approved source.

/.well-known/ · /agents.md · /capabilities.json

SAFE WRITES

Read freely.
Write with authority.

Every public change has an exact revision, confirmation boundary, and receipt. An agent can prepare work, but it cannot silently expand its authority.

PROPOSED→REVIEWED→APPROVED→PUBLISHED→VERIFIED

OUTCOME RECEIPTS

Keep the evidence chain intact.

Observed answers, website changes, agent actions, and CRM outcomes remain separate records. That keeps measurement useful and claims honest.

10:31answer.observedsaved

11:04change.approvedrevision 14

11:08change.verified_live200 OK

14:42action.completedcrm receipt

Give every AI agentthe same approved answer.

Update once.Keep every answer current.