Skip to content
Locins
Create account

For developers

Build on Locins OS.

Bricks, building blocks for your business or your clients', plus Gates and Looks. Sign-in, consent, data and AI are already built.

Add the SDKRequest an app
auth.ts
import { LocinsAuth } from '@locins/id' const auth = new LocinsAuth({  clientId: 'YOUR_CLIENT_ID',  redirectUri: 'https://yourapp.com/callback',  scope: ['identity', 'adventures:read'],}) await auth.login()
A plug clicks into a plate with three building blocks

Three parts, clear boundaries.

  • Brick

    Functions on matched data, with rules, events and slots for the interface. Every function automatically becomes an MCP tool. A Brick never talks to a source directly.

  • Gate

    The connection to a source, mirrored, live or shared, with field mapping and actions as the only way back. A Gate contains no business logic.

  • Look

    Look, images, tone and decor for the Bricks' slots. A Look reads no data.

Bricks catalogue
check-in.brick.yaml
brick: check-inversion: 1.2.0liest: [Buchung, Gast, Objekt]schreibt: [Meldeschein]regel: buchung.status == bestaetigtmcp: automatisch

Five things you don't have to build.

  • Sign in with Locins: Locins Pass via OAuth 2.1 with PKCE, with the npm package @locins/id for web, React and Expo.
  • Consent: one scope per data type, in plain words on the consent screen, revocable at any time.
  • MCP: one address for your users' and businesses' AI.
  • Sharing: data products and skills via OpenSharing, live and without copies.
  • AI layer: all models through one interface, processed in the EU.
How Locins OS is built

Every function is a tool for AI.

Locins speaks the Model Context Protocol. An AI client gets one address and sees only the tools the user or business has granted.

Speech bubble connected by a cable to a plug plate
https://locins.com/api/v1/mcp

More than 210 tools

Clients
  • ChatGPT
  • Claude
  • any client that speaks MCP with OAuth
MCP in detail

Read data, use AI, all openly described.

  • OpenAPI: The entire Locins API as an OpenAPI file. Generate your clients instead of writing them by hand.
  • AI layer: You name the task, Locins picks the model in the EU. Connect in Locins AI (in development) is reachable through the same interface.
  • Webhooks: Booking, check-in and payment arrive at your systems as events.
Locins AI
openapi.json
"/api/v1/partner-app-requests/capabilities": {  "get": {    "summary": "Capability vocabulary for the landing form.",    "tags": ["PartnerAppIntake"]  }}

Test first, then review, then everywhere.

  1. 1

    Sandbox

    A test account with test data and your own keys. No real guests.

  2. 2

    Review

    We check against the five points for partners, such as only the data it needs, WCAG 2.2 AA and data in the EU with no training.

  3. 3

    Catalogue

    Your Brick, Gate or Look appears in the catalogue with the “Checked by Locins” label and runs in every Terminal that switches it on.

Pick your way in.

You can add the SDK right away. To run, your app needs a client ID, which you get through the request.

Rather talk first? Write to hello@locins.com, subject “Developers”.

Write an email