Downcity

Product · Federation SDK

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

Open Federation SDK Docs

Federation owns the backend runtime; Embassy is the user and admin client entry.

Reuse the agent product backend layer

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

Unify models, accounts, usage, and payments

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

Keep local validation and deployment aligned

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

Typical Scenarios

  • 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/localfed or templates/edgefed for different runtime targets.

Facts

  • Core package: @downcity/federation
  • Core source directory: packages/federation/
  • Management entry: fed / downfed