Integrate with AI

Give your coding assistant a focused starting point with your repository open. Choose your task, stack and features, then copy the prompt or download Markdown. Use Official TypeScript SDK for a Node.js backend, or HTTP API directly for another language. Neither option requires a new service.

Generated from the published releaseSDK 0.13.0 · API 1.0.0 · 51 operations

TaskStart an integrationAdd a featureReview an integrationApplication stackUse the existing stackNext.js / ReactReact + Node.js backendNode.js backendOther backend languageIntegration methodOfficial TypeScript SDK (recommended for Node.js)HTTP API directly

Features in scope

Select only what you need. Administrative operations are optional and privileged.

Public market discoveryLive charts and order booksMultilingual market displaysAccounts and identityMarkets and tradingBalances and depositsPositions and redemptionWithdrawalsReferrals and rewardsRealtime account updatesWebsite trafficReporting and fee administration

Copy promptDownload Markdown

Generated locally in your browser. No project details or credentials are sent anywhere.

Prompt preview

Snapshot edcfc9a48736. Saved prompts do not update themselves; regenerate before starting a new integration.

How to use it

1. Select Start an integration, Add a feature, or Review an integration.
2. Select only the features you need. For a feature addition, the prompt preserves the existing integration; review prompts do not authorize changes.
3. Paste the generated prompt into your coding assistant with your project open. Let it inspect your existing stack and read the linked contract and guides first.
4. Supply approved environment details through your normal secure configuration—not in the prompt. CRISP credentials remain server-side.
5. Review the resulting diff, isolated tests and remaining integration steps. A generated prompt is not approval to trade, transfer funds, migrate production data or deploy.

Current integration patterns

Generated prompts recommend the shared application client for public market data and createAccountSync() for account updates. They distinguish public Polymarket streams from authenticated CRISP account realtime and explain dashboard origin registration. Fee displays use the active fee program. Webhooks require separate assessment and enablement rather than being a standard integration prerequisite.

Tied to the release, not a separate API description

Operation IDs, HTTP methods, routes, idempotency requirements and success statuses come directly from the published OpenAPI contract. The SDK name, version and available methods are checked against the actual downloadable package. The prompt release manifest records artifact and guide fingerprints. API payloads remain in the contract instead of a second set of hand-written examples.

Release synchronization regenerates these inputs. Tests and production builds reject stale artifacts, removed SDK helpers and unclassified new API operations. Task guidance is human-maintained and reviewed; these checks detect drift, but do not replace semantic API tests or engineering review.

A copied prompt is a snapshot. It tells the assistant to compare its fingerprint with the current manifest and regenerate if the release has changed. If your assistant cannot browse, provide the matching contract, SDK archive and guides; do not ask it to guess missing details. Local previews use local documentation links—generate from the deployed docs when sharing externally.

Continue with the runnable quickstart, SDK reference, or launch checklist.