This is the usual pattern for a hosted API: the product site explains the plan; a payment processor takes the card; a gateway issues the key. Same hop as geometry.app/pricing.
Checkout path
- Open Pricing (or follow an upgrade link after a quota
429). - Upgrade / Get a Free sandbox key opens the official Zuplo Developer Portal (same URL as below). Create the portal account, pick a plan, and subscribe.
- Stripe Checkout collects the card. After pay, the portal shows your subscription and a raw key (
zpka_…). - Paste the key onto the branded MCP URL — Where your key goes. The tool URL stays
https://mcp.geometry.app/mcp(never a*.zuplo.appMCP host).
Official Developer Portal
This is the production checkout host. geometry.app/pricing Upgrade and Get a Free sandbox key open the same page. The hostname is assigned by Zuplo. It is the official portal, not a lookalike.geometry-main-bf0a4d2.zuplo.site is Zuplo’s assigned Production Developer Portal. That vendor host is expected. It is not the MCP tool URL. Do not use *.zuplo.app for tools — that was a temporary gateway host. Tools stay at https://mcp.geometry.app/mcp.
You still call tools at
mcp.geometry.app. Zuplo sits in front as the gateway; Stripe never appears on the tool URL.
After you have a key
How-to for?key=, rotation, and cancel lives on Where your key goes. Billing card issues stay in the Stripe portal (opened from the Developer Portal).
Lookups (not a public database)
Tool answers are hosted Postgres lookups. Builders call MCP/HTTP tools only — there is no public SQL console and no table REST API.Plans
Same tools and fields on every tier. You pay for volume, not features. Current prices: geometry.app/pricing.Related
- Where your key goes — paste
?key=, roll a leak, cancel - Support — self-serve first; GitHub Issues for paid product bugs only
- Privacy · Terms — named processors