sofiastage.com valid

SofiaStage Agent API

Read-only index for SofiaStage cultural-event data exposed by the Cloudflare Worker API.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T14:13:18.543Z. Cached copy · Source on sofiastage.com

# SofiaStage Agent API

> Read-only index for SofiaStage cultural-event data exposed by the Cloudflare Worker API.

Use this file as a compact navigation layer for agents. Use OpenAPI for full schema and field-level details.

## Policies
- All public GET /v1/* endpoints are read-only and do not require user authentication; POST /v1/admin/sync is disabled and returns 410.
- The public MCP server at https://api.sofiastage.com/mcp exposes five read-only tools, two resources and three user-selected prompts with no authentication or user-specific data.
- /v1/events uses cursor pagination; cursors are valid only for the same filter set.
- Supported include values are stars and extras.
- Event, venue and title queries default to scope=sofia; use scope=all for every city or city=<name> for one city.
- Date format is YYYY-MM-DD and date_from must be <= date_to.
- Start-time filters: starts_after and starts_before are inclusive and support HH:mm, local YYYY-MM-DDTHH:mm with tz (default Europe/Sofia), or RFC3339 with offset/Z.
- limit values above 100 are clamped to 100; the /v1/cities lookup accepts up to 1000 so callers can build complete city indexes.
- Rate guidance: keep automated traffic polite (about 1-3 requests/second per client) and use exponential backoff on 429/5xx responses.
- Caching guidance: respect Cache-Control and stale-while-revalidate headers (meta: 30s, events: 60s, lookups/details: 300s, discovery docs: 3600s).
- Stability guidance: /v1/* read endpoints and response envelopes are stable integration targets; /v1/admin/sync is outside normal public read workflows.
- Attribution guidance: preserve canonical_url/info_url/ticket_url fields when redistributing results and attribute SofiaStage as the aggregator.
- Non-ASCII query values (for example Cyrillic) must be URL-encoded by the client.
- Extras content fields (article, bottom_article) are Markdown.
- Star/extra slug detail routes rely on snapshots; missing snapshot rows return 404.

## Core
- [OpenAPI schema](https://sofiastage.com/api/openapi.json): Complete machine-readable contract.
- [MCP server](https://api.sofiastage.com/mcp): Stateless Streamable HTTP endpoint for event search, detail and catalog/profile tools.
- [Health check](https://sofiastage.com/api/health): Liveness and deploy status.
- [Metadata](https://sofiastage.com/api/v1/meta): Snapshot/version metadata and record counts.
- [Events feed](https://sofiastage.com/api/v1/events): Primary collection with filtering and pagination. Defaults to Sofia; add scope=all or city=... for other cities.
- [Events example (upcoming + includes)](https://sofiastage.com/api/v1/events?limit=25&include=stars,extras): Starter query that remains current as snapshots advance.
- Date/time-window recipe: set date_from and date_to to the same current YYYY-MM-DD, then add starts_after and/or starts_before with tz=Europe/Sofia.
- [All-city title search example](https://sofiastage.com/api/v1/events?title=%D0%9A%D0%B0%D1%80%D0%BB%D1%81%D0%BE%D0%BD
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=sofiastage.com · GET /v1/domain/sofiastage.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for sofiastage.com:
1. POST https://agentwebmap.com/v1/sites/sofiastage.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://sofiastage.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/sofiastage.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/sofiastage.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.