Reuseio API quick reference

Catalog endpoints#

GET /productsPaginated public Product list.

GET /providersProvider list.

GET /capabilitiesCapability taxonomy.

GET /tagsTag taxonomy.

GET /search?q=...Keyword search over the catalog.

Request conventions#

The public API uses standard HTTPS and JSON responses. Use GET for catalog, product, and source reads; use POST /research when the request body needs to express task-level research conditions. Production callers should set timeouts, inspect status codes, limit log content, and cap pagination explicitly.

Safety boundaryA public read endpoint does not mean callers may send internal data. Submit only the abstract task and public keywords required for retrieval.

Product endpoints#

GET /products/{slug}Complete Product details.

GET /products/{slug}/manifestMachine-friendly Manifest.

GET /products/{slug}/sourcesSource list.

GET /products/{slug}/evidence?field=...Field-level Evidence.

GET /products/{slug}/ai-promptPrompt for Coding Agents.

Research endpoint#

The research endpoint uses POST because the request body needs to express a task, required capabilities, preferred capabilities, a maximum candidate count, and fallback options.

curl -X POST 'https://reuseio.com/api/v1/research' \
  -H 'Content-Type: application/json' \
  -d '{
    "task": "Build private object storage with signed downloads",
    "required_capabilities": ["object storage", "signed downloads"],
    "preferred_capabilities": ["Node SDK"],
    "max_products": 8
  }'

Compose the workflow#

In an application, endpoints are commonly composed as “search → details → Manifest → sources and evidence”. Search discovers, details explain relationships, Manifest serves machine reads, and Sources and Evidence support review. This prevents a short search result from becoming final configuration by accident.

Build a candidate setCall search or catalog endpoints and keep the slug and match reason.
Read the standard viewUse details or Manifest to get capabilities, integrations, and implementation constraints.
Review the evidenceOpen Sources and Evidence to confirm that critical decisions align with official documentation.

Status codes#

200Request succeeded.

400Invalid parameters.

404Resource not found.

429Too many requests.

500 / 503Internal error or source temporarily unavailable.