Build a catalog workflow

Use this workflow when several callers share the same choices. Catalog endpoints require a bearer API key in the current contract.

Create the catalog

Choose an ID that is stable in your application. The ID may contain letters, numbers, ., _, and -, and may be up to 128 characters long.

cURL

curl https://api.aspaslabs.com/v1/catalogs \
  -X POST \
  -H "Authorization: Bearer $ASPAS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "support-actions",
    "model": "goldenfish-g1",
    "choices": [
      "reset_password",
      "billing",
      "cancel_account",
      "technical_issue"
    ],
    "version": "20261011.120000",
    "visibility": "private"
  }'

The response contains the catalog ID, model, choices, version, and visibility.

Read the catalog

cURL

curl https://api.aspaslabs.com/v1/catalogs/support-actions \
  -H "Authorization: Bearer $ASPAS_API_KEY"

Use this endpoint to verify the current definition before a deployment or to build an internal configuration view. It is not a dashboard endpoint; there is no hosted dashboard for managing catalogs yet.

Use the catalog in a decision

Replace the inline choices array with catalog:

cURL

curl https://api.aspaslabs.com/v1/decisions \
  -H "Authorization: Bearer $ASPAS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "goldenfish-g1",
    "input": "I was charged twice for the same order.",
    "instruction": "Which support action applies?",
    "catalog": "support-actions"
  }'

The decision request must not include choices and catalog together. The model in the decision request should match the catalog’s model.

Delete a retired catalog

cURL

curl https://api.aspaslabs.com/v1/catalogs/support-actions \
  -X DELETE \
  -H "Authorization: Bearer $ASPAS_API_KEY"

A successful delete returns 204 No Content. Remove the catalog from application configuration only after all callers have migrated or stopped using it.

Change management

Treat catalog changes like code changes:

Review additions and removals.
Update the version label.
Test representative inputs against the new choices.
Deploy the new catalog and caller together when possible.
Keep the previous definition in your own change history if you need to interpret old decisions.

Get started

Concepts

Guides

API reference

Resources

Create the catalog

Read the catalog

Use the catalog in a decision

Delete a retired catalog

Change management

​Create the catalog

​Read the catalog

​Use the catalog in a decision

​Delete a retired catalog

​Change management

Create the catalog

Read the catalog

Use the catalog in a decision

Delete a retired catalog

Change management