Intellifi Nl Brain Web API

Name: Brain Web API
Brand: Intellifi Brain Web API
Availability: InStock

✓ Official Vendor SpecIOTDevice ManagementapiKey77 EndpointsREST

For Agents

Read and write to an Intellifi Brain instance — manage devices, locations, items, presences, key-value pairs, and uploaded blobs for RFID and Bluetooth asset tracking.

Install Jentic One Beta

Connect the Brain Web API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Brain Web API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Brain Web API.

Inspect the authenticated session via GET /authinfo to confirm permissions

Upload, download, and delete binary blobs through /blobs and /blobs/{id}

Stream and query device events through /events

GET STARTED

Start building with Brain Web API

Explore with Jentic

View OpenAPI Document

The Brain Web API is the REST surface of Intellifi's Brain platform, a localisation system for items and assets that uses RFID and Bluetooth devices. Across 77 endpoints, the spec covers device and location management, key-value storage, presences and items, blob upload and download, events, and user-defined location rules — the core building blocks for tracking physical assets in a warehouse, retail, or logistics environment. Authentication can be a query API key, a header API key (X-Api-Key), or a session cookie, and the base URL is templated per customer Brain instance.

Use Cases

Patterns agents use Brain Web API for, with concrete tasks.

★ Warehouse Asset Tracking Dashboard

Pull presences, items, and locations from a customer Brain instance and render them in a warehouse dashboard so operators can see where every RFID-tagged asset is at any moment. The /presences and /items endpoints provide the live state, while /events offers a stream of changes for animation or alerting.

List items via /items, locations via /locations, and presences via /presences, then render the live mapping in the operations dashboard.

Custom Location Rule Provisioning

Use /locationrules to encode business rules such as 'high-value tools must not leave bay 4' and combine them with device-event streams to detect violations in real time. The Brain stores the rules per customer instance, so a tooling layer can provision them as part of customer onboarding.

POST a new rule via the locationrules endpoint and listen on /events for matching device telemetry.

Configuration and Blob Storage

Store device firmware blobs or per-customer configuration files via POST /blobs, retrieve them through GET /blobs/{id}, and download named files via /blobs/{id}/download/{filename}. This lets the Brain double as a small artifact store for the assets connected to it.

POST a new blob with the firmware payload, then store the returned blob id against the target device.

AI Agent Operations Console via Jentic

An AI agent given access to a customer Brain through Jentic can answer questions like 'where is asset 1234' or 'what events happened on device 9 in the last hour' by calling the Brain endpoints by intent. Jentic isolates the API key and templates the customer subdomain in the base URL, so the agent only handles structured operational data.

Through Jentic, call brain_get_presences for the asset id and brain_list_events for the relevant device, then summarise the location and recent activity.

Key Endpoints

77 endpoints — the brain web api is the rest surface of intellifi's brain platform, a localisation system for items and assets that uses rfid and bluetooth devices.

METHOD

PATH

DESCRIPTION

GET

/authinfo

Inspect the current session

GET

/blobs

List uploaded blobs

POST

/blobs

Upload a new blob

GET

/blobs/{id}

Retrieve a blob's metadata

DELETE

/blobs/{id}

Delete a blob

GET

/events

List device and system events

GET

/authinfo

Inspect the current session

GET

/blobs

List uploaded blobs

POST

/blobs

Upload a new blob

GET

/blobs/{id}

Retrieve a blob's metadata

DELETE

/blobs/{id}

Delete a blob

GET

/events

List device and system events

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Intellifi Brain X-Api-Key is stored encrypted in the Jentic vault and bound to the request header at execution time. The customer-specific base URL is held alongside it, so the agent never builds the URL or holds the key directly.

Intent-based discovery

Agents search Jentic by intent (for example 'list Intellifi presences for an asset' or 'upload an Intellifi blob') and Jentic returns the matching operation across the 77 endpoints with its input schema.

Time to first call

Direct integration: 2-3 days to wire multi-scheme apiKey auth, templated base URL, and the 77-endpoint surface across items, locations, presences, and events. Through Jentic: under 1 hour.

FAQs

Specific to using Brain Web API through Jentic.

What authentication does the Intellifi Brain Web API use?

The spec defines three apiKey schemes: QueryApiKey (query parameter 'key'), HeaderApiKey (header 'X-Api-Key'), and CookieSid (a session cookie named 'brain.sid'). Endpoints accept any of these. Through Jentic, the API key is held in the encrypted Jentic vault and bound to the X-Api-Key header at execution time.

Can I list which items are at which locations?

Yes. The /presences endpoint returns the live mapping between items and locations as observed by the Brain's RFID and Bluetooth devices. Combine with /items and /locations for human-readable metadata.

Can I store binary blobs against the Brain?

Yes. POST /blobs uploads a blob, GET /blobs/{id} reads metadata, /blobs/{id}/upload adds further uploads, /blobs/{id}/download/{filename} retrieves the file, and DELETE /blobs/{id} removes it.

What are the rate limits for the Intellifi Brain Web API?

The OpenAPI specification does not encode explicit rate limits. Each Brain is a per-customer deployment, so capacity depends on the customer instance. Avoid tight polling on /events — use longer intervals or stream consumers — and back off on 429 responses if seen.

How do I query asset presence through Jentic?

Run pip install jentic, then have the agent issue the search-load-execute flow with the query 'list Intellifi presences for an asset'. Jentic returns the operation backed by /presences; the agent supplies the asset id filter and receives the current location mapping.

What does the templated base URL look like?

The servers entry is {protocol}://{customer}.intellifi.{tld}/api, so each customer's Brain has its own subdomain. Provide protocol (http or https), customer subdomain, and tld at execution time; Jentic stores these alongside the API key for the configured Brain instance.

Intellifi Nl Brain Web API

Connect the Brain Web API to your agent

Capabilities

Start building with Brain Web API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs