Skip to main content

Developers

Regeneration and cache control for your content workflow

Create API keys in the dashboard and integrate the two shipped external capabilities into publishing or CI/CD workflows.

External API

Small, authenticated surface

Requests use a dashboard-created Bearer key and are scoped to domains owned by that key’s tenant. The production base URL is https://app.sigiledge.ai/api/v1/.

POST/api/v1/regenerate

Queue regeneration for one URL or an entire verified domain.

DELETE/api/v1/cache

Purge approved enrichment for one URL or all cached entries under a verified domain.

Regenerate one pagecurl
curl -X POST https://app.sigiledge.ai/api/v1/regenerate \
  -H "Authorization: Bearer sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "domain": "example.com",
    "url": "/products/trail-runner"
  }'

Keys are displayed once when created and stored as hashes. Revoked keys stop authenticating immediately. The API applies a per-key request limit.

Where the API fits

Keep enriched output aligned with changes in the source system.

Content publishing

Regenerate a product or article URL after the origin publishes an update.

Catalog refreshes

Queue a domain-wide refresh after a substantial source or template change.

Rollback workflows

Purge cached enrichment before or after configuration changes when fresh generation is required.

llms.txt

A concise content guide at the domain root

SigilEdge can serve tenant-configured content at /llms.txt. The convention is emerging and is not an access-control system, a training-policy enforcement mechanism, or a guarantee of indexing or attribution.

Use it for

  • • A short site or organization description
  • • Links to important documentation or content areas
  • • Human-readable context for machine consumers

Explore the live product surface

Open the dashboard to manage keys, domains, regeneration, and usage.

Open DashboardStart Early Access