OPEN PLATFORM

Let your service
be called by REACHE on users' behalf

REACHE is an AI companion that helps users run real life. By integrating with the Open Platform, when a user says "book / check / handle this for me…", REACHE — at the right moment and with the user's authorization — calls your service directly and gets it done, giving you a brand-new natural-language entry point.

Apply to integrate See how it works

Why integrate

Not just another API marketplace. REACHE turns your capabilities into actions a user can trigger with a single sentence.

Lang

Natural-language entry

Users don't need to open your app or hunt for a button. They state a need, REACHE understands the intent and calls you directly — zero interface friction.

Ctx

Context-aware calls

REACHE knows the user's schedule, preferences, and location. It calls you with the context ready, yielding far higher conversion than a cold start.

Trust

User authorization, fully controllable

OAuth authorization, minimal scopes, mandatory confirmation for sensitive actions, revocable at any time. User trust is what makes the partnership last.

Four steps to integrate

Reuse REACHE's mature Skill engine — all you need to do is declare a tool manifest.

Register your app

Declare your tools

Write a Tool Manifest: what it does, what parameters it takes, and which endpoint to call.

User authorization

Users grant access with one tap in the Authorization Center, using standard OAuth 2.0.

Get called

REACHE automatically selects the tool, extracts parameters, confirms, calls it, and brings the result back into the conversation.

// A Tool Manifest looks like this
{
  "tool_id": "acme.book_table",
  "name": "Book a restaurant table",
  "description": "Book by restaurant, party size, and time. Use when the user says 'book a table' and gives a restaurant name.",
  "params_schema": { /* JSON Schema:restaurant / datetime / party_size */ },
  "endpoint": "https://api.acme.com/reache/book_table",
  "scopes": ["acme.booking.write"],
  "sensitive": true,
  "confirm_prompt": "Confirm booking with Acme: {restaurant}, {datetime}, party of {party_size}?"
}

Safety & boundaries

REACHE's core red lines are also the hard rules of the Open Platform.

Money and irreversible actions always require the user's explicit approval.Sensitive tools — placing orders, payments, sending outbound messages — always prompt for confirmation before calling. REACHE never pays on the user's behalf.

Minimal scope + revocable.Only the necessary scopes are granted; users can revoke anytime in the Authorization Center, and revocation takes effect immediately.

Domain allowlist + outbound validation.Data is sent only to the endpoints you declare, preventing any leakage.

Honest about failure.When a call fails, REACHE tells the user it didn't go through — never falsely claims success.

Roadmap

Establish the spec and portal first, confirm direction, then build the backend — avoiding rework.

P1 · In progress

Spec + portal

This page + integration spec, gathering interest from the first wave of developers.

Tool registration backend

Manifest validation + end-to-end flow with first-party tools.

OAuth authorization

Full authorize/revoke loop, integrated with the Authorization Center.

Self-service publishing

Developer self-service + review console + auditing, officially open.

Apply to integrate

Leave your service details and contact, and we'll invite you to join the first wave of co-builders.

Submit interest

Let your servicebe called by REACHE on users' behalf