← All action domains

Web

1 operation. Call each with POST https://app.chirply.io/api/v1/actions/<name> and a bearer token; the response is { "data": { "action", "summary", "result" } }. A read badge means the operation changes nothing; write requires the credential’s write scope.

Search the web

web.searchread

Search the public internet and get a short, sourced answer: current facts, news, prices, opening hours, weather, a company's details, anything outside this account. Returns the answer and the web pages it came from. Reads nothing about the account and changes nothing. Runs on the account's own OpenRouter key, which OpenRouter bills for the model call plus its live web results (a few cents per search at most).

Parameters

FieldTypeRequiredDescription
querystringrequiredWhat to look up, in plain words — a question or keywords, e.g. "weather in Austin tomorrow" or "Acme Plumbing Dallas phone number".

Example

curl -X POST https://app.chirply.io/api/v1/actions/web.search \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "example"
  }'
Test with your API key

Over MCP the same operation is the tool web_search at https://app.chirply.io/api/mcp, same bearer token, same input.

The machine-readable version of this page is GET https://app.chirply.io/api/v1/actions?domain=web — same operations, with full JSON Schemas. Authentication, errors and rate limits are covered in the API documentation home.