Loading...
Product
Core Features
Top Extensions
Company
Subscribe to our newsletter.
Get product updates and news in your inbox. No spam.
Search the CeyPay documentation, REST API reference, blog, and changelog without leaving your keyboard.
CeyPay lets Sri Lankan merchants accept cryptocurrency and settle in Rupees. This extension puts the integration docs, the full API surface, and the latest product news one keystroke away.
Fuzzy-search every guide, integration page, and reference page. Filter by section with the dropdown. Press ↵
to read a page inside Raycast, or ⌘ ↵ to open it in the browser.
Browse all CeyPay REST endpoints, grouped by resource. Each endpoint shows its parameters, request body, and response examples in the detail pane — no browser round-trip. Search by endpoint name, path fragment, or operation id.
| Shortcut | Action |
|---|---|
↵ | Open the endpoint's documentation |
⌘ ⇧ P | Copy the path |
⌘ ⇧ U | Copy the full production URL |
⌘ D | Toggle the detail pane |
The action panel also offers Copy as cURL for both the production and sandbox hosts, pre-filled with the authentication headers the API expects.
Browse posts from the CeyPay blog as a grid of cover images. Filter by tag, press ↵ to read the post inside
Raycast, or ⌘ ↵ to open it on the site.
Product and legal updates as one row per entry, newest first, with its release date and tags. Press ↵ for the
full entry including screenshots, or ⌘ ↵ to open its permalink on the docs site.
Docs and API search run entirely offline against assets/index.json, which ships inside the extension. Nothing
is fetched while you type, so results are instant and search keeps working without a network connection.
The index is a snapshot, not a live feed. assets/index.json is committed to the repository and shipped inside
each extension release, so new or renamed docs pages and API endpoints only show up in search after a new
version of this extension is published — they are not picked up automatically in between. Page content is
always current, because opening a result fetches the page from docs.ceypay.io at read time; it is the
searchable list of pages and endpoints that follows the release cycle. Blog posts and changelog entries are
fetched live and are never affected by this.
Regeneration is conditional, not automatic. npm run build runs build:index first, but that script rebuilds
the index only when it finds a CeyPay docs checkout (a sibling docs/ directory, or DOCS_DIR). Without one it
prints a notice, keeps the committed snapshot, and lets the build continue — so the extension builds anywhere,
but a release is only as fresh as the last commit of assets/index.json. Refreshing it is a deliberate step for
a maintainer with the docs repository checked out, described under Regenerating.
If a page you expect is missing, it most likely landed in the docs after the last release — please open an issue and a refreshed index will go out with the next version.
Network requests happen only when you open something:
docs.ceypay.io.docs.ceypay.io and splits them into entries.ceypay.io/blog, never the private Ghost domain.Both docs sources are MDX rather than plain Markdown, so src/lib/mintlify.ts converts the components Raycast
cannot render — cards, accordions, steps, callouts, HTML tables — into Markdown it can.
The index is generated from the docs repository rather than scraped from the live site:
docs.json supplies the navigation, so each page lands in the right section and group..mdx file supplies its title and description from frontmatter.api/v1/openapi.json supplies every endpoint, and each operation's x-mint.href supplies its canonical
documentation URL.npm run build:index # expects the docs repo as a sibling directory
DOCS_DIR=/path/to/ceypay-docs npm run build:index
npm run build:index -- --no-verify # skip the live-URL check
By default the script verifies every indexed URL against the live site and reports any that are not reachable yet. A batch of 404s means the deployed docs are behind the docs repo — deploy, then re-run.
npm run build runs this step first, so a maintainer who has the docs repository checked out ships a fresh
index. In a checkout without it, the step is a no-op that keeps the committed assets/index.json and the build
proceeds — regenerate before cutting a release if the docs have moved on.
npm install
npm run dev
The index is derived data. To fix a wrong title or description, change it in the docs repository and
regenerate — do not hand-edit assets/index.json.