Product · City SDK

Bring model catalogs, service routing, auth, runtime env, usage, balance, and payment capabilities into your agent product stack.

City remains the current SDK and package name, so implementation docs keep that name.

Reuse the agent product backend layer

Organize services, actions, auth, env, and access boundaries once instead of rebuilding the backend for every AI product.

Let multiple agents, products, or workflows reuse one model catalog, account service, usage ledger, and payment flow.

Use one service composition across local validation, Node deployment, and edge deployment.

• Multi-product reuse: let multiple agent products share accounts, models, usage, and payment services.
• Service access: call Service actions in City from frontend, extension, or backend code without coupling to database internals.
• Deployment composition: use templates/node or templates/edge for different runtime targets.