API reference

https://actify-api.vercel.app

On /v1/* endpoints, send your partner API key using either header (Bearer is recommended):

Authorization: Bearer <api_key>
X-API-Key: <api_key>

Keys are issued per integration. To start onboarding, rotate a key, or get integration help, email api-actify@outlook.com.

Runs purchase-intent detection and product retrieval. Returns either an empty object {} or a single optional extension field, _commerce_layer.

{
  "task_query": "which microphone is best for podcasting?",
  "context_metadata": {
    "service_name": "research_agent",
    "user_locale": "en-US"
  }
}

Only these top-level fields are accepted. Extra keys return HTTP 422.

{
  "_commerce_layer": {
    "status": "match_found",
    "recommendations": [
      {
        "id": "0a1b2c3d-4e5f-6789-abcd-ef0123456789",
        "product_id": "prod_sm7b",
        "title": "Shure SM7B",
        "url": "https://actify-api.vercel.app/r/0a1b2c3d-4e5f-6789-abcd-ef0123456789",
        "price": 399.0,
        "currency": "EUR"
      }
    ]
  }
}

curl -X POST "https://actify-api.vercel.app/v1/match" \
  -H "Authorization: Bearer $ACTIFY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"task_query": "which microphone is best for podcasting?"}'

Latency and client timeouts

• Parallel execution. Start the match call alongside your own work — wall time tracks the slower branch, not the sum.
• Variable round-trip. From your infrastructure, HTTP responses are often roughly 1–4 s; cold paths can approach ~4 s. Your network and platform matter as much as ours.
• Client timeout. Always finite. Tune to when you emit the response — ~1–2 s is a practical default for many stacks; shorter caps (e.g. ~400 ms) are aggressive fail-open and may miss in-flight results on fast handlers or cold starts.
• Internal intent gate uses a bounded stage budget on the order of ~800 ms — that does not cap every end-to-end HTTP duration.

Invoked when someone opens a recommendation URL. Returns 302 to the merchant with click logging. 404 if the id is unknown or expired — issue a fresh match call instead of retrying the same URL.

No API key is required on this endpoint.

Limits & reliability