Raycast AI API

AI access surfaced through the SDK via `AI.ask(prompt)` - no API keys or HTTP endpoint required. Routes prompts across 80+ models from OpenAI, Anthropic, Google, Mistral, Groq, Perplexity, and xAI behind the Raycast Pro / Advanced AI subscription. Available only inside extensions through the @raycast/api library, not as a standalone REST API.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/raycast-ai-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

raycast-openapi.yml Raw ↑
openapi: 3.0.1
info:
  title: Raycast Extension API (SDK)
  description: >-
    Raycast's developer surface is NOT a public HTTP REST API. It is the
    @raycast/api TypeScript/Node SDK (installed with `npm i @raycast/api`) used
    to build Raycast extensions with React. Capabilities - AI (`AI.ask`),
    Storage, Cache, Clipboard, Preferences, OAuth, Environment, Window
    Management, Menu Bar Commands, and Browser Extension - are exposed as
    SDK modules and React components invoked from inside an extension's
    process, not as network endpoints. There is no documented public base URL,
    no request/response HTTP contract, and no authenticated REST surface to
    model. This OpenAPI document therefore intentionally declares an empty
    `paths` object: it exists to register the provider in the API Evangelist
    catalog and to make the SDK-based nature of the interface explicit. No REST
    endpoints have been fabricated. Developers should consult the SDK reference
    at https://developers.raycast.com/api-reference for the actual TypeScript
    API.
  termsOfService: https://www.raycast.com/terms
  contact:
    name: Raycast Developers
    url: https://developers.raycast.com/
  version: '1.0'
servers:
  - url: https://developers.raycast.com
    description: >-
      Documentation host only. Raycast does not expose a public REST API base
      URL; the SDK runs locally inside extensions.
paths: {}
components:
  schemas: {}