Pixela API
Official vendor OpenAPI document · agent-readyAnalyticsWeb AnalyticsapiKey26 EndpointsREST
For Agents
Programmatically create a new user, update a user. Covers 26 operations with apiKey authentication.
Use for: I need to a new user, I want to a user, Search for a user, Find all view user profile
Not supported: Does not handle payments, communications, or crm - use for analytics only.
API for recording and tracking habits or effort, routines. Pixela provides graph-based tracking of daily activities with SVG visualizations. The API exposes 26 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Pixela API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pixela 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.
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%2Fpixe.la%2Fpixe" | 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%2Fpixe.la%2Fpixe" | 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 Pixela API.
Create a new user
Update a user
Delete a user
View user profile
Get all graph definitions
Use Cases
Patterns agents use Pixela API for, with concrete tasks.
★ Analytics Operations
Use the Pixela API to perform analytics operations programmatically. The API provides 26 endpoints covering core functionality including create a new user, update a user, delete a user.
Call POST /v1/users to create a new user
Automated Users Management
Automate users operations by combining multiple Pixela API endpoints. Agents can update a user and then delete a user in a single workflow.
Call PUT /v1/users/{username} to update a user, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Pixela API 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 apiKey tokens manually.
Search Jentic for 'create a new user', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
26 endpoints — api for recording and tracking habits or effort, routines.
METHOD
PATH
DESCRIPTION
POST
/v1/users
Create a new user
PUT
/v1/users/{username}
Update a user
DELETE
/v1/users/{username}
Delete a user
GET
/@{username}
View user profile
PUT
/@{username}
Update user profile
POST
/v1/users/{username}/graphs
Create a graph definition
GET
/v1/users/{username}/graphs
Get all graph definitions
GET
/v1/users/{username}/graphs/{graphID}
Get graph SVG
POST
/v1/users
Create a new user
PUT
/v1/users/{username}
Update a user
DELETE
/v1/users/{username}
Delete a user
GET
/@{username}
View user profile
PUT
/@{username}
Update user profile
POST
/v1/users/{username}/graphs
Create a graph definition
GET
/v1/users/{username}/graphs
Get all graph definitions
GET
/v1/users/{username}/graphs/{graphID}
Get graph SVG
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Pixela by hand means sending its X-USER-TOKEN header on every call, threading the username through each path, and handling retries yourself. Through Jentic you install once, import Pixela from the API Directory, store the token once, and your agent calls it.
Permission scoping
Pixela puts the username and graph id in the URL path (/v1/users/{username}/graphs/{graphID}), so a rule can pin your agent to one user and its graphs. You choose the operations it may call, so deleting a user is not included unless you add it.
Credential isolation
Your Pixela user token is stored once, encrypted, by your own Jentic One instance and injected as the X-USER-TOKEN header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a pixel graph' or 'record today's value', and Jentic returns the matching Pixela 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.
FAQs
Specific to using Pixela API through Jentic.
What authentication does the Pixela API use?
The Pixela API uses an API key passed in the `X-USER-TOKEN` header. 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 create a new user with the Pixela API?
Yes. Use the POST /v1/users endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Pixela API?
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 create a new user through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new user'. Jentic returns the matching Pixela API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Pixela API have?
The Pixela API exposes 26 endpoints covering users, profiles, graphs operations.
Can I limit what my agent is allowed to do with the Pixela API?
Yes. Because you run Jentic One yourself, your own rules decide which Pixela operations and credentials the agent may use. Since Pixela carries the username and graph id in the URL path, such as /v1/users/{username}/graphs/{graphID}, you can pin the agent to a single user and its graphs. You also choose the exact operations it may call, so a destructive action like deleting a user stays off the list unless you add it.
GET STARTED