Model an event's location, event record, and eventDate hierarchy before selling tickets on Weeztix (formerly Eventix)
domain: weeztix.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a location resource for the event first, since Weeztix events attach to a location.
Create the event resource itself, referencing that location.
Attach an eventDate resource to assign the actual date/time slot(s) the event runs on.
Create ticket resources and attach them to the eventDate using Weeztix's resource-attachment pattern.
Known gotchas
Eventix rebranded to Weeztix — older 'Eventix API' references and the eventix.io domain point to the same underlying platform, so use current material under docs.weeztix.com.
The docs.weeztix.com portal is a client-rendered app; confirm exact endpoint paths and required fields directly in that portal rather than assuming REST conventions.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?