AI Solutions Exchange
Get started
Integration API · v1

One API. Every editor.

AI Solutions Exchange is editor-agnostic. All business logic lives in a shared backend — AI analysis, setup wizards, security labels, and compatibility scores are generated once and served through the same public API to VS Code, Cursor, Windsurf, JetBrains, and any third-party plugin. Build a thin adapter, not a backend.

Unified manifest

Capability, permissions, execution type, and readiness in one neutral schema.

Security & policy

Enterprise risk, security labels, and org policies enforced consistently everywhere.

Setup wizards

Render creator-defined wizards natively in any editor; submit answers via API.

Endpoints

Base URL: https://aisolutions.exchange

GET/api/public/schema

Enums and constants used across the platform: execution types, permissions, security labels, environments.

GET/api/public/prompts?q=&category=&risk=&limit=

Discover published solutions. Returns compact rows with slug, pricing, ratings, enterprise risk, and per-environment scores.

GET/api/public/prompts/:slug/manifest

Full capability manifest for one solution: execution type, permissions, security labels, enterprise risk, readiness report, environment compatibility.

GET/api/public/prompts/:slug/wizard

Setup-wizard schema for the solution, plus estimated setup time and compatibility score.

POST/api/public/prompts/:slug/wizard/submit

Submit buyer answers and receive the rendered, tailored prompt. Requires an API key.

Authorization: Bearer sk_live_...
Content-Type: application/json

{
  "wizard_id": "...",
  "answers": { "api_base_url": "https://...", "team_name": "Acme" }
}

Authentication

Read endpoints are public. Any mutation (currently: wizard submission) requires an API key. Send it as an HTTP bearer token:

curl -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"wizard_id":"...","answers":{}}' \
  https://aisolutions.exchange/api/public/prompts/your-slug/wizard/submit
Manage your API keys

Build an editor adapter

An editor extension is a thin renderer over this API. Typical flow:

  1. Call /api/public/prompts to list or search.
  2. Load /api/public/prompts/:slug/manifest. Enforce your org's policy against permissions and security_labels.
  3. Render the environment_scores for your editor.
  4. If a wizard exists, fetch /wizard and render each field in native UI.
  5. POST answers to /wizard/submit. Use the returned rendered_prompt in-editor.

The schema is stable across editors. Adding VS Code, Cursor, Windsurf, or JetBrains support is a client-only change — no backend work required. Third parties are welcome to ship their own plugins against these endpoints.