API platform

API Platform

Developer quickstart

Start with the production boundary, learn the session model, then build against contracts that WEDNESDAY explicitly supports.

Get started API reference

HTTP · verify production availability

curl -sS https://api.wednesdaychat.com/health
# {"status":"ok"}

Production boundary: most product operations are authorized through a WEDNESDAY server account session. The public API origin is documented; a general third-party API-key program is not implied until WEDNESDAY explicitly releases one.

Build paths

Platform and API

Understand durable state, streaming, projects, files, search, errors, rate limits, and the verified HTTP surface.

Start with the platform ↗

Agents and tools

Build around typed tool execution, project context, research, connectors, approvals, and observable runtime state.

Explore agents ↗

Models

WEDNESDAY routes work through stable execution profiles while retaining freedom to improve the upstream provider route behind those profiles.

Balanced

BalancedProduction

Responsive general-purpose work with balanced reasoning and latency.

Deep

Deep reasoningProduction

Higher-reasoning execution for complex analysis and difficult multi-step work.

Code

CodingProduction

Code-oriented routing for software-development-heavy tasks.

Start building

◯Durable conversation statePersist and recover conversations rather than treating every request as isolated. ⌁Structured streamingRender typed model and tool events while work is still in progress. ✦Tool-using applicationsExtend model execution with bounded tools, search, files, research, and connectors. ◇Project contextScope instructions, files, connectors, conversations, and work history to a project. ▣Files and LibraryUpload, inspect, attach, retrieve, and manage account-owned files. ◎Long-running researchTrack research as durable task state rather than one fragile request.

Production resources

Production best practices

Retries, durable reconciliation, readiness, security boundaries, and release discipline.

Security

Authority, account scope, connector boundaries, and safe public-contract rules.

Machine-readable docs

llms.txt, consolidated docs, Markdown twins, search index, sitemap, and crawler guidance.

Status

Check WEDNESDAY service health and incident communication independently of this documentation site.

One source of truth

Public documentation is a production compatibility surface. Technical claims are published only when traceable to production behavior, a verified production specification, or another explicitly versioned public contract. Internal topology, secrets, provider routing, roadmap-only functionality, and privileged operational procedures stay out of the public corpus.