Publishing Data to QANATIX Open

Make your business data discoverable by AI agents worldwide. Publishing to QANATIX Open is free for all QANATIX Engine plans.

How it works

1. You upload data normally via the QANATIX Engine API
2. You set visibility: "public" on records you want to share
3. Public records are automatically indexed in the unified Open search index
4. Any AI agent can now discover and query your data — no auth required

Your data stays in your private tenant too. Publishing simply sets visibility — your private search still works as before.

Prerequisites

• A QANATIX Engine account (any plan, including Free)
• Data already uploaded and active

Set record visibility

On creation

Include visibility when uploading data:

curl -X POST https://api.qanatix.com/api/v1/upload/manufacturing/product/batch \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "name": "Ball Bearing 6205",
      "description": "Deep groove ball bearing, 25mm bore",
      "visibility": "public",
      "collection_data": {"manufacturer": "SKF", "price_eur": 8.50}
    }
  ]'

Toggle existing records

# Make a single record public
curl -X PATCH https://api.qanatix.com/api/v1/records/{record_id}/visibility \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"visibility": "public"}'

# Bulk update — up to 1,000 records at once
curl -X POST https://api.qanatix.com/api/v1/records/bulk-visibility \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "record_ids": ["uuid-1", "uuid-2", "uuid-3"],
    "visibility": "public"
  }'

Set collection default

Make all new records in a collection public by default:

curl -X PATCH https://api.qanatix.com/api/v1/collections/manufacturing/default-visibility \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"default_visibility": "public"}'

New records in the manufacturing collection will default to visibility: "public". Existing records are not affected — use bulk-visibility to update them.

Making data private again

curl -X PATCH https://api.qanatix.com/api/v1/records/{record_id}/visibility \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"visibility": "private"}'

The record is immediately removed from the Open collection. It may appear in cached results for up to 30 seconds, but the Postgres hydration layer filters it out.

Provider analytics

When your public data appears in Open search results, QANATIX tracks it:

curl https://api.qanatix.com/api/v1/usage \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

The response includes open_searches — the number of times your data was returned in Open queries this month.

What gets published

When an record is set to visibility: "public", the following fields are visible in Open search results:

Best practices

1. Start with a subset — publish a sample, monitor analytics, then expand
2. Use meaningful descriptions — description_llm powers full-text search. Better descriptions = better discoverability
3. Fields are auto-detected from your data — no schema registration needed
4. Keep data fresh — stale data reduces trust
5. Don't publish sensitive data — once public, anyone can query it