smart-me
Browse all Smart Me APIs★ Only Publicly Available OpenAPI DocumentIOTDevice Managementbasic64 EndpointsREST
For Agents
Programmatically creates a access token to write on a card (e.g. nfc), post-api-account-login. Covers 64 operations with basic authentication.
Use for: I need to creates a access token to write on a card (e.g. nfc), I want to post-api-account-login, Search for account_login, Find all set an action for the specified device.
Not supported: Does not handle payments, communications, or crm - use for iot and hardware only.
With the smart-me REST API you get Access to all your devices in the smart-me Cloud and you can add your own devices. So its an easy way to add the smart-me Cloud support to your Hardware or Software Product. The API exposes 64 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the smart-me to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the smart-me, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsmart-me.com%2Fsmart-me" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsmart-me.com%2Fsmart-me" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 smart-me API.
Creates a Access Token to write on a Card (e.g. NFC)
post-api-account-login
Account_Login
Set an action for the specified device.
Gets all available Actions of a Device
Use Cases
Patterns agents use smart-me API for, with concrete tasks.
★ IoT and Hardware Operations
Use the smart-me to perform iot operations programmatically. The API provides 64 endpoints covering core functionality including creates a access token to write on a card (e.g. nfc), post-api-account-login, account_login.
Call PUT /api/AccessToken to creates a access token to write on a card (e.g. nfc)
Automated AccessToken Management
Automate accesstoken operations by combining multiple smart-me endpoints. Agents can post-api-account-login and then account_login in a single workflow.
Call POST /api/Account/login to post-api-account-login, then verify the result
AI Agent Integration via Jentic
AI agents discover and call smart-me endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.
Search Jentic for 'creates a access token to write on a card (e.g. nfc)', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
64 endpoints — with the smart-me rest api you get access to all your devices in the smart-me cloud and you can add your own devices.
METHOD
PATH
DESCRIPTION
PUT
/api/AccessToken
Creates a Access Token to write on a Card (e.g. NFC)
POST
/api/Account/login
post-api-account-login
GET
/api/Account/login
Account_Login
POST
/api/Actions
Set an action for the specified device.
GET
/api/Actions/{id}
Gets all available Actions of a Device
GET
/api/AdditionalDeviceInformation/{id}
Gets the additional information (e.g. Firmware Version) about a device.
POST
/api/CustomDevice
Creates or updates a Custom Device or updates it's values.
GET
/api/CustomDevice
Gets all Custom Devices
PUT
/api/AccessToken
Creates a Access Token to write on a Card (e.g. NFC)
POST
/api/Account/login
post-api-account-login
GET
/api/Account/login
Account_Login
POST
/api/Actions
Set an action for the specified device.
GET
/api/Actions/{id}
Gets all available Actions of a Device
GET
/api/AdditionalDeviceInformation/{id}
Gets the additional information (e.g. Firmware Version) about a device.
POST
/api/CustomDevice
Creates or updates a Custom Device or updates it's values.
GET
/api/CustomDevice
Gets all Custom Devices
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring smart-me by hand means handling its basic auth against smart-me.com, tracking device and action ids, and managing retries yourself. Through Jentic you install once, import smart-me from the API Directory, store the credential once, and your agent calls it.
Permission scoping
smart-me puts the resource id in the URL path (/api/Actions/{id}, /api/AdditionalDeviceInformation/{id}), so a rule can pin your agent to one device or action: it can read that resource and nothing else. You choose the operations it may call, so writes like creating a custom device are not included unless you add them.
Credential isolation
Your smart-me credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read a device's values' or 'trigger a device action', and Jentic returns the matching smart-me operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe
Complementary API for broader integration workflows
Use alongside smart-me for multi-service workflows
FAQs
Specific to using smart-me API through Jentic.
What authentication does the smart-me use?
The smart-me uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I creates a access token to write on a card (e.g. nfc) with the smart-me?
Yes. Use the PUT /api/AccessToken endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the smart-me?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I creates a access token to write on a card (e.g. nfc) through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a access token to write on a card (e.g. nfc)'. Jentic returns the matching smart-me operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the smart-me have?
The smart-me exposes 64 endpoints covering accesstoken, account, actions operations.
GET STARTED