OpenWebAPI

The API layer for the web

OpenWebAPI

Make any website programmable. Turn public web workflows into clear API actions your app, agent, or internal tool can call without building a custom integration for every site.

Submit a website Browse catalog
Input
Any public domain
Layer
Website actions
Use
Apps and agents

Who it helps

For teams building on top of the open web.

The web is full of useful data and actions, but most sites are designed for people, not software. OpenWebAPI gives products a programmable layer over those public experiences.

AI

AI app builders

Give agents a small set of named website actions instead of asking them to browse, click, and guess.

Use it when an agent needs reliable public web context or a next step.

PM

Product teams

Bring public website workflows into your product without designing a custom integration for every site.

Use it for search, lookup, comparison, planning, and research flows.

DEV

Platform teams

Offer teams one consistent API pattern for websites instead of a pile of one-off scrapers.

Use it to standardize how internal tools consume public web data.

What users can do

Ask websites for outcomes, not raw pages.

Each website becomes a set of named capabilities: search, read, compare, check, extract, and hand off to the official source when a human should finish the flow.

Search

Find things on a site

Query catalogs, listings, documentation, directories, schedules, and other public search surfaces.

Read

Turn pages into data

Extract titles, summaries, links, fields, tables, and details your product can display or summarize.

Compare

Check options and state

Normalize public page state like availability, status, dates, prices, requirements, and locations.

Handoff

Send users to the right place

Build official deep links or next-step URLs when the user should finish the workflow on the source site.

How it feels

Choose a website, call an action, show the result.

Start from the catalog when the website already exists. Submit a domain when you need a new public site covered. The end result is a predictable API surface over the web.

  1. 01

    Pick

    Choose a website and action from the catalog.

  2. 02

    Call

    Send the small JSON input the action asks for.

  3. 03

    Use

    Show the structured result or chain it into the next step.

website action
POST /websites/{domain}/tools/{action}/execute
{
  "query": "what the user needs",
  "filters": {
    "location": "optional"
  }
}

200 OK
{
  "source": "official website",
  "results": [
    { "title": "structured result", "url": "https://..." }
  ],
  "next": "open official flow"
}