API Terms

Current status

Urbs has no public API, API keys or MCP server for customers yet. The web app calls its own internal endpoints. These aren’t a supported interface, can change without notice, and mustn’t be called from scripts, tools or other applications; doing so breaches our Terms of Service.

If you need programmatic access, email tamas@urbsai.com and tell us what you’re trying to do.

When an API launches

We’ll update this page before any API becomes available. Our Terms of Service will still apply, and the API terms will cover at least:

• Keys and access: keys belong to one account, must be kept confidential, and mustn’t be shared or published in code.
• Rate limits and fair use: published request limits for each key, and no getting around them with extra keys or accounts.
• Redistribution: what you may display, store, cache and pass on to your own users, set for each data source and type of output. Some data may be viewable but not exportable or redistributable.
• Attribution: attribution and licence notices returned with data must stay with it and be shown to anyone you share it with.
• Your obligations: using the data lawfully, including under privacy and marketing laws, and not using it to build a competing dataset.
• Changes: notice periods for breaking changes, and how old versions will be retired.

Redistribution today

What can be redistributed depends on each source’s licence, which we’re reviewing source by source and for each way data leaves Urbs. Until that review is complete for a source, its data may only be shared as our Terms of Service allow: within your organisation, and as small attributed extracts.