Everything you need to publish, and nothing you need to ask for
Cabuya is a document and a validator. There is no account to create, no key to request, and nobody to negotiate with — including us.
The five-minute version
Publish a JSON file describing your places at a stable URL, and a small manifest at a known path stating who you are. Serve both with `Access-Control-Allow-Origin: *`, run the validator against them and correct what it reports. That is conformance at L2, and for a small application it is an afternoon.
One schema, four transports
The same place record moves four ways. Which one you serve is an operations decision; the record does not change, so a consumer written against one works against the others.
Three ways in
Most teams arrive wanting one of these. They are independent — publishing does not require consuming, and neither requires the agent skill.
Publish
Export what you already have in the shared schema, and let anyone read it.
You run an application with places, needs or capacities in it
Consume
Read other publishers’ feeds under the consumption rules, with attribution intact.
You want more coverage than your own data gives you
Teach an agent
Install the skill and your coding agent knows the protocol, offline, with the spec vendored.
You would rather have an agent do the integration