garden.checkout.create(...)Create a hosted or embedded checkout session.
Build billing into your product. Bring your own agents into the financial conversation. GardenKit, Planter and the Keystone contract provide clear integration boundaries for the work.
Clover, here is the revenue context for our next month-end review.
Let’s pick up the conversation and compare the periods.
New L1fe applications integrate through Keystone for identity, access and billing. Framework adapters keep the application boundary consistent.
Explore Keystone ↗The billing SDKCheckout, usage, invoices, payment methods and webhooks behind one typed TypeScript surface.
Explore GardenKit ↗The embedded experienceBring the billing workspace into a React application through the Planter components and server data adapters.
Explore Planter ↗garden.checkout.create(...)Create a hosted or embedded checkout session.
garden.portal.link(...)Create a customer billing portal link.
garden.usage.ingest(...)Record usage with a stable event identity.
garden.invoices.list(...)Read invoices for the scoped customer.
garden.paymentMethods.list(...)Read the account's payment methods.
garden.webhooks.route(...)Verify and route incoming billing events.
The product vision connects agents outside Garden through authorized API and MCP integrations. Use the relevant service contract for the operation, with identity and access supplied through the platform boundary.
Keep me in the loop when an invoice changes.
Auth owns identity and sessions. IAM owns roles, grants and entitlements. Garden owns billing accounts, usage, invoices, wallets and plans. Applications use the Keystone contract to bring those pieces together.
@l1fe/keystone@l1fe/keystone-next@l1fe/keystone-tanstack@l1fe/keystone-vite@l1fe/garden/keystoneThe GardenKit adapter connects tenant context to checkout, usage ingestion and portal links.
GardenKit exposes entrypoints for Next.js, Hono, Express and Keystone. Configure your authorized API endpoint, account context and credentials on the server.
GardenKit includes webhook verification and routing helpers. Use the configured secret and current service contract, with durable duplicate handling appropriate to your deployment.
Explore webhooksExplore the available developer tools and service-specific integration contracts. Agent access follows the permissions configured for your workspace.
Explore the agent experienceKeystone is the application-facing platform contract for identity, access and billing. GardenKit is the typed Garden billing SDK and includes a Keystone adapter.
Configure privileged credentials on your server. Pass the appropriate account context through the platform integration and keep secrets out of browser bundles.
No. The website preview uses sample data. Your available developer tools and services depend on your account and deployment.
Explore Planter, the React billing experience exported from @l1fe/garden/planter, with data helpers in @l1fe/garden/planter/server.