The Bily model
Connected customer data
Collect and normalize website events once so browser, server, and AI workflows share a dependable context.
Trusted routing
Route data through explicit website, organization, and store boundaries.
Governed activation
Run supported reads and actions through authenticated developer surfaces with clear scope.
Bily Apps
Install and evolve reusable capabilities through the Bily connection a site already maintains.
How the developer surfaces fit
The JavaScript SDK is the browser contract. It installs Bily once and sends page, product, checkout, and custom events. The Bily API is the server contract. It lets your own tools read scoped analytics and store state, and perform supported actions with explicit authentication. The Bily MCP is the AI-client contract. It lets compatible clients discover the current operation catalog and run scoped work with Bily authentication. All three surfaces connect to the same Bily layer. The API and MCP enforce Bily identity, organization, and store access for authenticated server and AI work.Designed to evolve
Bily gives your team one stable foundation for customer data, activation, safety, and observability. You can adopt Bily Apps without repeatedly rebuilding your website integration. Your team keeps control of:- which sites and stores are connected;
- which Bily Apps are installed and enabled;
- which organization can access each store;
- which API keys can read data or perform actions;
- when a Bily App or configuration reaches customers.
Install the SDK
Connect a website and send your first event.
Explore Bily Apps
Review the installable capability layer built for the Bily connection.
Call the Bily API
Authenticate a server request and discover your stores.
Connect an AI client
Connect through Bily MCP and discover supported operations.