Pixelixe API
✓ Official Vendor SpecMediaImage ProcessingapiKey4 EndpointsREST
For Agents
Programmatically test api key, search documents. Covers 4 operations with apiKey authentication.
Use for: I need to test api key, I want to documents, Search for generate an image from a template (image automation api), Find all apply filters and photo effects
Not supported: Does not handle payments, communications, or crm — use for media and content only.
The Pixelixe API allows developers to search and manage design documents, automate image generation from templates, and apply filters and processing operations to images over HTTP. The API exposes 4 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Pixelixe API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pixelixe 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Pixelixe API.
Test API key
Search documents
Generate an image from a template (Image Automation API)
Apply filters and photo effects
Use Cases
Patterns agents use Pixelixe API for, with concrete tasks.
★ Media and Content Operations
Use the Pixelixe API to perform media operations programmatically. The API provides 4 endpoints covering core functionality including test api key, search documents, generate an image from a template (image automation api).
Call GET /api/authentication/v2 to test api key
Automated Authentication Management
Automate authentication operations by combining multiple Pixelixe API endpoints. Agents can search documents and then generate an image from a template (image automation api) in a single workflow.
Call GET /api/document/search/v2 to search documents, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Pixelixe 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 'test api key', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — the pixelixe api allows developers to search and manage design documents, automate image generation from templates, and apply filters and processing operations to images over http.
METHOD
PATH
DESCRIPTION
GET
/api/authentication/v2
Test API key
GET
/api/document/search/v2
Search documents
POST
/api/graphic/automation/v2
Generate an image from a template (Image Automation API)
GET
/api/photo/effect/v2
Apply filters and photo effects
GET
/api/authentication/v2
Test API key
GET
/api/document/search/v2
Search documents
POST
/api/graphic/automation/v2
Generate an image from a template (Image Automation API)
GET
/api/photo/effect/v2
Apply filters and photo effects
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Pixelixe API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'test api key') and Jentic returns the matching Pixelixe API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Pixelixe API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Pixelixe API through Jentic.
What authentication does the Pixelixe API use?
The Pixelixe API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I test api key with the Pixelixe API?
Yes. Use the GET /api/authentication/v2 endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Pixelixe 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 test api key through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'test api key'. Jentic returns the matching Pixelixe API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Pixelixe API have?
The Pixelixe API exposes 4 endpoints covering authentication, document, graphic operations.
GET STARTED