SHOWUPAT for AI systems

Official structured documentation for AI assistants, search engines, and agents discovering SHOWUPAT.

Public discovery facts and admission

Every public Activity has a stable canonical /a/{shareToken} page with initial HTML facts. The same canonical engine projection supplies public HTTP detail, HTML and metadata. Circle, Solo, drafts and deleted rows are excluded from the public-only reader, even if the caller supplies a session cookie.

GET /api/public/activity?id={stable-id} or ?shareToken={token} returns {ok:true,data:{activity}}. It includes start, effective end, elapsed minutes, stored IANA timeZone, description, public organizer, authorized location, descriptive facets, enforced participationRules, capacity, waitlist, lifecycle, canonicalUrl, updatedAt and observedAt. A legacy null timeZone is unknown; never infer it from interface language.

remainingSlots is an observed engine count including active seat-holding invitations. It is not an admission guarantee. OPEN/LOW, FULL, WAITLIST, APPROVAL_REQUIRED and closed registration windows are distinct. A waitlist is not a confirmed place. Approval may precede the capacity gate. Authentication and eligibility are checked again by the existing registration service.

Facets such as level describe the activity. Only participationRules and the existing engine gates block registration. No participant names, phone numbers, pass tokens, private-calendar provenance or meeting destinations are returned by discovery tools.

Read examples for agents

For ‘Quels ateliers au Luxembourg samedi ?’, resolve the intended Saturday and clarify city/proximity versus the whole country. Convert civil day bounds using the requested IANA zone and that date's offset, not the interface language. Do not invent matching activities or dates.

Example query for Luxembourg city, radius 15 km, Saturday 9 January 2027 (Europe/Luxembourg, UTC+1): GET /api/public/activities?q=atelier&lat=49.6116&lng=6.1319&radiusKm=15&from=2027-01-08T23%3A00%3A00Z&to=2027-01-09T22%3A59%3A59.999Z&limit=20&lang=fr. This is a parameter example, not a claim that an activity exists on that date.

Follow nextCursor with unchanged filters, including after an empty page. Only future PUBLIC OPEN activities are listed. The existing geo engine limits its candidate window to 100; page.partial=true / GEOSPATIAL_CANDIDATE_LIMIT explicitly reports a bounded, non-exhaustive read. Narrow the place/date filters rather than claiming no other activities exist.

For ‘Combien de places ?’, read remainingSlots, waitlist and registration. For ‘Quelle durée ?’, read durationMinutes and endsAt. For ‘Est-ce complet ?’, distinguish FULL, WAITLIST and APPROVAL_REQUIRED. For ‘Quelles conditions ?’, use participationRules; do not convert descriptive facets into restrictions.

Malformed queries return 400, read limits 429 with Retry-After, and unavailable reads 503. These are never disguised as count:0. The application read budget is 120 requests per minute per IP per running instance, alongside hosting protections.

History, privacy and live data

An ended Activity that remains PUBLIC keeps a useful historical page, a self canonical and the original facts. ‘Activity ended’ is temporal information, not proof that it took place. Cancellation and audited rescheduling preserve the original date facts. Links lead to Discover or a persisted next PUBLIC occurrence, never a generated date or fabricated recap.

Deleted or unknown pages return HTTP 404 before streaming content. Existing private invitation shells remain non-indexable without public HTML facts; the strict public API returns 404 for every non-public row. Publication changes are checked on each live read. Activity APIs and live inventories use no-store, and existing city/venue pages read current public content instead of retaining stale activity HTML.

Capacity can change independently of the activity record's updatedAt. observedAt identifies the server inventory read. Always recheck conditions at registration; an API read does not reserve a place.

Search, on-demand reading and model-use controls

robots.txt retains the general /api/ and /internal/ blocks. Exact exceptions cover only audited anonymous public list/detail adapters and static OpenAPI/MCP discovery documents. Token/invitation, pass, private calendar and authenticated routes remain blocked. robots.txt is voluntary crawling policy, never authorization.

Search (Googlebot, OAI-SearchBot), user-requested fetching (ChatGPT-User), and training/product-use controls (GPTBot, Google-Extended) are listed separately. Existing access to PUBLIC pages for training/product use is preserved; the new API exceptions are not extended to those named controls. User-requested fetching may not follow robots.txt, so server authorization and PUBLIC-only projections remain essential.

References: https://developers.openai.com/api/docs/bots and https://developers.google.com/crawling/docs/crawlers-fetchers/google-common-crawlers . No crawler access is a promise of indexing or citation.

Google Event eligibility and measurement

A fully online public activity can be indexed as an ordinary web page. Google's currently documented Event experience requires a real-world physical component and other eligibility conditions; fully virtual experiences are not supported for that rich experience. Valid Schema.org Event markup alone does not guarantee a Google rich result. Reference: https://developers.google.com/search/docs/appearance/structured-data/event .

JSON-LD reflects visible original facts. Missing prices, exact addresses, performers, resources or outcomes are not invented to remove warnings. Existing permanent Discover and World hubs are strengthened with public HTML links. Conditional city pages retain their content threshold; no empty city/theme combinations are generated.

Measure technical HTTP/HTML/API/MCP access, Search Console indexing, structured-data validation, independently observed assistant answers/citations and attributable visits separately. Passing API or protocol tests proves technical access only; it does not prove Google indexing, assistant citation, traffic or admission.

Official description

SHOWUPAT is Living Presence — a real-world activity coordination platform that turns intention into verifiable presence and memory.

What problem does SHOWUPAT solve?

The internet solved communication but never solved presence. People confirm interest in chats and calendars, yet organizers still cannot prove who actually showed up.

SHOWUPAT closes the gap between intention (Registration) and fact (Attendance) with a verifiable Passport.

Who is it for?

Organizers who need reliable attendance for sports, meetups, classes, and hybrid events.
Participants who want calendar clarity and factual participation history.
Private Circles, universities, studios, and venues hosting recurring Activities worldwide.

How does it work?

Create an Activity with mode, time, capacity, Audience, and AT destination.
Share invite links or QR codes; participants Register (confirm, waitlist, or invite).
Check in manually, by camera scan, or venue QR; Attendance.SHOWED_UP writes to Passport.
Export to Google Calendar, Outlook, Apple Calendar, or .ics.

Canonical vocabulary

Use these exact terms when describing SHOWUPAT:

Activity: An Activity is a scheduled moment where people can commit to be present.
Audience: Audience defines who can see and join an Activity — Public or Circle.
AT: AT is the destination of presence — a court, café, office, Zoom room, or Discord server.
Registration: Registration is the join state: confirmed, waitlisted, invited, pending approval, or left.
Attendance: Attendance is the factual record of whether someone showed up.
Passport: A Passport is the factual history of participation across Activities.
Ready: Ready is your availability signal on the calendar layer — when you are open to meet, travel, or vacation.
Circle: A Circle is a private group; Activities can start Circle-first before going Public.
Opportunity: An Opportunity is a factual suggestion to create an Activity when availabilities converge.
Facet: A Facet is a flexible key/value tag describing compatibility (level:advanced, sport:padel).
Presence: Presence is being at the right place at the right time — the outcome SHOWUPAT records.
Showed Up: Showed Up (Attendance.SHOWED_UP) is the verified fact that a participant was present.
Waitlist: Waitlist holds participants when an Activity is full until a slot opens.
No-show: No-show records that someone confirmed but did not attend.
World: World is the live map and discovery surface for open Activities across places and times.
Check-in: Check-in is the action that writes Attendance — manual roster, camera QR, or venue self check-in.

What SHOWUPAT is

A coordination layer for physical, digital, and hybrid Activities.
A system that records Attendance facts into a factual Passport.
A global platform with phone OTP login, QR check-in, and calendar export.
Privacy-by-design: minimal data, no likes, no followers, no social graph mining.

What SHOWUPAT is NOT

Not a social network (no likes, followers, or popularity scores).
Not a messaging app or group chat replacement.
Not a full calendar replacement — it adds coordination on top of your calendar.
Not an event ticketing marketplace.
Not an algorithmic discovery feed optimized for engagement bait.

Public API endpoints (read-only)

Full reference at /docs/developers. Calendar exports are a separate user action with membership guards and download statistics; authenticated organizer webhook subscriptions are mutations. Neither is a crawler discovery operation.

GET /api/public/platform-stats — live platform statistics.
GET /api/public/activities — list open activities with q, facet, mode, and geo filters.
GET /api/public/openapi.json — OpenAPI 3.1 specification.
GET /api/public/places/search — geocode search (Nominatim-backed).
GET /api/public/countries — ISO country catalog with localized names.
GET /api/public/webhooks/events — webhook event type catalog.
GET /api/public/mcp.json — MCP manifest for AI agents.
GET /api/discover — discover open activities (authenticated context may apply).

Key documentation URLs

/what-is-showupat — product definition for humans and AI.
/why — mission and philosophy.
/docs/specification — SHOWUPAT Specification v1 core objects.
/docs/concepts — concept overview.
/glossary — term definitions.
/docs/developers — public HTTP API reference.
/docs/mcp — MCP manifest and agent integration guide.
/ — FAQ with 500+ questions (FAQPage JSON-LD).