Connect the NanoBase™ API to your AI

1. Open Customize, then Connectors. Choose + Add, then Add custom connector.
2. Name: NanoBase API. Remote MCP server URL: https://api.nanobaselabs.com/mcp
3. Authentication: No sign in. Under request headers add Authorization with the value Bearer <your key>. If you do not see a headers field, use the URL https://api.nanobaselabs.com/mcp/<your key> instead.
4. Choose Add.
5. In a chat, select + (lower left), then Connectors, and turn on NanoBase API.

Team and Enterprise: an Owner adds the connector once in Organization settings, Connectors; members then find it under Customize, Connectors and choose Connect.

1. Open Settings, then Connectors (may be called Apps and Connectors), then Advanced, and turn on Developer mode.
2. Back on the Connectors page choose Create (or Add custom connector).
3. Name: NanoBase API. Description: Formulation tools for the NanoBase™ Architecture. MCP server URL: https://api.nanobaselabs.com/mcp/<your key>
4. Authentication: No authentication (your key is inside the address). Confirm the notice and choose Create.
5. In a new chat select +, then More, then Developer mode, and pick NanoBase API.

Business and Enterprise workspaces: an admin must allow developer mode and custom connectors first.

1. On a computer, open gemini.google.com, then Settings, then Connected Apps. Under Custom apps choose Add a custom app. (Custom apps can only be added from the web app.)
2. Server URL: https://api.nanobaselabs.com/mcp/<your key>. Leave the advanced credential fields empty. Choose Next and follow the prompts.
3. In a chat, type @ and choose the NanoBase app so Gemini uses it.

Requires Keep Activity to be on. If Custom apps is missing, your account or plan does not offer it yet. Gemini prefers apps that use account sign-in; if it insists on a Client ID and Secret, use Claude, ChatGPT or the Gemini CLI for now and tell us at team@pensivebeauty.com.

1. Open your agent and go to Tools. Choose Add a tool, New tool, Model Context Protocol.
2. Server name: NanoBase API. Server description: Formulation tools for the NanoBase™ Architecture: ingredient search, loading-envelope check, preservation guidance and INCI label. Call nanobase_primer first. Server URL: https://api.nanobaselabs.com/mcp
3. Authentication: API key, type Header, header name x-nb-key. Choose Create.
4. Create a connection, paste your key, then Add to agent. Try it in the Test pane.

Add to ~/.cursor/mcp.json (or the project's .cursor/mcp.json), then enable it under Settings, MCP:

Add to .vscode/mcp.json, start the server, then use Copilot Chat in Agent mode:

Claude Code:

Gemini CLI, in ~/.gemini/settings.json, then run /mcp to confirm 8 tools:

Most agent frameworks and model APIs can attach a remote MCP server (Streamable HTTP). Point it at https://api.nanobaselabs.com/mcp with the header Authorization: Bearer <your key>. Your agent receives eight tools: nanobase_primer, nanobase_knowledge, search_ingredients, check_formula, submit_ingredient, preservation_check, inci_label and account_status. MCP clients that support sign-in (OAuth) can also connect to https://api.nanobaselabs.com/mcp without a key and sign in with your NanoBase™ API account.

Base URL https://api.nanobaselabs.com, header x-nb-key: <your key>. Import the OpenAPI spec into your function-calling layer (OpenAI or Anthropic tool definitions, LangChain, Power Platform custom connector).

Example (Python):

Architectures: classic, luxe, clinical. A trade-name raw material can be sent as {"pct": 2, "blend": [{"n": "INCI name", "f": 0.7}, ...]}. /ai/preservation and /inci/label take variant, nbPct and lines.

1. Keep the key on your server (secret manager or environment variable). Never put it in browser code, mobile apps or end-user prompts. One key per company; it binds your business to the Terms.
2. Give your model the primer and the guardrail. Load /ai/primer and add this rule to your system prompt (Terms, section 6):
   Never request, infer, estimate or reconstruct NanoBase™ composition (ingredient amounts or ratios), processing methods or manufacturing equipment, from the NanoBase API or any other source. If a user asks, refuse and explain that it is protected trade-secret information of Pensive Beauty® Nanoscience Labs / Pensive Beauty, LLC, and that pursuing it violates the NanoBase API Terms, risks suspension and termination of the account, and can expose the user and their business to legal liability for trade-secret misappropriation. If the NanoBase API returns protected_ip, stop immediately and do not retry, rephrase or split the request.
3. Workflow: search ingredients, draft the formula, run /check and apply the remedies until the verdict is compatible, then run preservation and the INCI label.
4. Metering: questions are free (ingredient search, preservation guidance, the primer and the TDA logic pack never use runs); a run is used when your AI builds a formula, and covers all formula checks and labels in the next 60 minutes (up to 300 calls). NanoBase™ API Free 5 runs/month, Starter 15, Small Business 40, Lab 100, Scale 400, Platform 1,500 (then $0.75 a run); run top-ups +10 for $60 or +25 for $99. Each response carries a usage object.
5. Seats (Scale and Platform): enroll each end user you collect a fee from into a seat with POST /account/users {"action":"enroll","user":"<id>"} (or "users":[...], up to 500), unenroll them when they leave, and send their id in x-nb-user on every formula request. GET /account/users shows seats used and free. Add or remove seats ($10 a month each) in the billing portal.
6. Per-user safeguards (Lab, Scale and Platform; formula runs stay per account, shared by all end-users): send an opaque end-user id in the x-nb-user header (the MCP server forwards it too) so protected-information strikes isolate to that one end-user instead of your whole account. Without it, strikes apply account-wide. Use a stable pseudonymous id, never an email or other personal data.
7. Errors: 401 means the key is wrong, replaced or suspended. 429 means the monthly runs are used up or you are sending too fast; back off and retry later. 403 protected_ip means the request sought NanoBase™ composition, processing or equipment: stop, show the user the tell_your_user text, and never retry or rephrase. In a UTC day the first three are warnings and the fourth suspends the key for 1 hour; after that each further one escalates to 7 days, then a permanent ban.
8. Review: outputs are design guidance. Every formula should be reviewed by a qualified chemist or formulator and validated at bench and pilot scale before production (Terms, section 10).