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. Endpoint paths below are relative to the production base URL https://app.sigiledge.ai/api/v1.

POST/regenerate

Queue regeneration for one URL or an entire verified domain.

DELETE/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.

CI/CD

Queue regeneration from the pipeline that ships the content

Add the call as the last step of the job that deploys your content, so enriched output is refreshed by the same run that publishes the change.

Refresh after a content deployGitHub Actions

# .github/workflows/publish.yml
name: Publish content

on:
  push:
    branches: [main]

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Build and deploy site
        run: ./scripts/deploy.sh

      - name: Regenerate SigilEdge enrichment
        env:
          SIGILEDGE_API_KEY: ${{ secrets.SIGILEDGE_API_KEY }}
        run: |
          curl -fsS -X POST https://app.sigiledge.ai/api/v1/regenerate \
            -H "Authorization: Bearer $SIGILEDGE_API_KEY" \
            -H "Content-Type: application/json" \
            -d '{
              "domain": "example.com"
            }'

Store the key as a repository or environment secret and read it from the step environment, never commit it to the workflow file. curl -f makes the step fail if the request is rejected. To refresh a single page instead of the whole domain, add a url field as shown in the request above.

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 Dashboard Start Early Access