E-commerce

Connect StoreCensus

Manage StoreCensus orders, products, and customers via API.

E-commerce

StoreCensus

Manage StoreCensus orders, products, and customers via API.

Available
API keyScoped proxy

Connect with a provider API key

The client enters their provider key in the hosted connect flow. CybrLink stores it in the credential layer, then agents call through scoped MCP/API access without seeing the raw secret.

Where to get your StoreCensus API key
Connect in portal

Step 1

Open the portal connect flow

Step 2

Enter the provider API key

Step 3

Create a scoped MCP/API key

Sample request

// 1. Mint a session token for the end user
const session = await link.connect.session({
  integrationKey: "store-census",
  userId: "u_42",
});

// 2. After the user enters their provider API key, proxy a request
const res = await link.proxy("store-census", "u_42", {
  method: "GET",
  endpoint: "/api/v1/me",
});

More in this category

StoreCensus + AI agents: common questions

How do I connect StoreCensus to an AI agent?
Create a free CybrLink account, open the dashboard, and click Connect on StoreCensus. You authorize once with an API key; CybrLink stores the credential in its token vault and your agent reaches StoreCensus through the CybrLink MCP server or the agent proxy API. The credential itself is never placed in the model's context.
Does StoreCensus work with Claude, GPT, and other MCP clients?
Yes. CybrLink exposes a remote MCP (Model Context Protocol) server, so any MCP-capable client or agent framework — including Claude, OpenAI-based agents, and custom agents — can call StoreCensus once you've connected it. Non-MCP agents can use the authenticated HTTP proxy instead.
Is it safe to give an AI agent access to StoreCensus?
CybrLink scopes every connection to the permissions you grant, keeps tokens out of the model, logs each call to an activity audit trail, and lets you revoke the StoreCensus connection at any time from the dashboard.