Skip to content
Everday

One engine. Every door open.

Everything Everday does runs through one permission-checked API, and everything the API can do, your agents can do over MCP. Your data, your keys, no side doors.

Get a key: early accessTalk to engineering →
terminal · sample
$ curl "$EVERDAY_API/v1/nodes?model=candidate" \
    -H "authorization: Bearer $EVERDAY_KEY"
{
  "data": [{
    "id": "nd_2f81",
    "model": "candidate",
    "values": { … },
    "provenance": { … }
  }]
}
sample data · docs arrive with your key

The API.

One REST surface (/v1): nodes, models, skills, views, sites. Everything scoped, everything permission-checked: the same door our own surfaces use. Typed SDK. The docs

one rest surface
  • /v1/nodes
  • /v1/models
  • /v1/skills
  • /v1/views
  • /v1/sites
scoped · permission-checkedThe docs

API parity, everywhere.

Everything the API can do, your AI can do over MCP: same permissions, same audit trail. Everday in your AI →

The CLI.

The same permission-checked surface, from your terminal: inspect your workspace, run and test agents, move config. Docs arrive with your key.

In, out, and events.

Connections read your world in and write intelligence back; webhooks tell your systems when things happen. Implemented connectors →

RecruiteeGreenhousePersonioBambooHRHiBobNotionSlackTwenty

The boundary.

  • 01External code never touches internals.
  • 02Your workspace’s vocabulary travels with the API: the models you defined, not generic HR objects.
  • 03And your data is exportable, always.

Get a key.

Get a key: early access→Talk to engineering