Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Creatica Backgrounds 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcreatica.app%2Fcreatica" | shStep 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%2Fcreatica.app%2Fcreatica" | 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.
What an agent can do with Creatica Backgrounds API.
List the 59 background structures and read each one's parameter schema
Browse built-in palettes with mood tags
Rank structures for a natural-language brief with the suggest endpoint
Render a deterministic SVG or PNG background from a structure, seed, and colours
Serve a cacheable image URL with width, seed, and colour options
GET STARTED
Patterns agents use Creatica Backgrounds API for, with concrete tasks.
★ On-Demand Background Generation
A design tool renders a background for a card or hero section on demand. The agent picks a structure, reads its parameter schema, and calls generate with a seed and colours, getting back a deterministic SVG or PNG that renders identically on every repeat so layouts stay stable.
Call GET /v1/backgrounds/{name}/schema to read the parameters, then POST /v1/generate with a seed and colours
Brief-Driven Structure Selection
Given a short natural-language brief, an agent asks the suggest endpoint to rank the available structures and pairs the top match with a palette whose mood tags fit. It then renders the chosen structure, turning a plain description into a usable background without a human picking from the catalogue.
Call GET /v1/suggest with the brief, read GET /v1/palettes for a matching palette, then POST /v1/generate
AI Agent Integration via Jentic
An AI agent reaches the Creatica Backgrounds API through Jentic and discovers the right structure by intent. It receives the generate operation and its input schema, supplies a seed and colours, and executes with the optional token injected at run time, embedding the returned image URL directly in its output.
Search Jentic for 'render a procedural background', load the POST /v1/generate schema, and execute it with Jentic-managed credentials
9 endpoints — the creatica backgrounds api generates deterministic procedural svg and png backgrounds on demand from 59 structure generators and curated palettes.
METHOD
PATH
DESCRIPTION
/v1/backgrounds
List structures
/v1/backgrounds/{name}
Describe a structure
/v1/backgrounds/{name}/schema
JSON Schema of a generate request
/v1/palettes
Built-in palettes with mood tags
/v1/suggest
Rank structures for a natural-language brief
/v1/generate
Render a background
/v1/render/{file}
Fetch a cacheable rendered image
/v1/backgrounds
List structures
/v1/backgrounds/{name}
Describe a structure
/v1/backgrounds/{name}/schema
JSON Schema of a generate request
/v1/palettes
Built-in palettes with mood tags
/v1/suggest
Rank structures for a natural-language brief
/v1/generate
Render a background
/v1/render/{file}
Fetch a cacheable rendered image
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Creatica by hand means handling its optional bearer token, reading each structure's parameter schema, and assembling seed and colour options for every render yourself. Through Jentic you install once, import Creatica from the API Directory, store any token once, and your agent calls it.
Permission scoping
Most operations are read-only catalogue and schema lookups, so a rule can allow those plus the single generate call the agent needs. You choose the operation set, so it renders backgrounds and reads structures without reaching anything else.
Credential isolation
Any Creatica token 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 'render a procedural background' or 'suggest a structure for a brief', and Jentic returns the matching Creatica operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Creatica Backgrounds API through Jentic.
What authentication does the Creatica Backgrounds API use?
The Creatica Backgrounds API declares a bearer token scheme in its OpenAPI spec, and calls may be made with or without it depending on the structure and plan. Through Jentic any token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Are the generated backgrounds reproducible with the Creatica Backgrounds API?
Yes. The same structure, options, and seed always render the same image, so an agent can regenerate an identical background later from the same inputs. Each structure also publishes a parameter schema so the agent can build a valid generate request.
Can I pick a background from a text description with the Creatica Backgrounds API?
Yes. The suggest endpoint ranks the available structures for a natural-language brief, and the palettes endpoint returns built-in palettes with mood tags to match. The agent can then render the top-ranked structure with a chosen palette.
How do I render a background through Jentic with the Creatica Backgrounds API?
Search Jentic for 'render a procedural background', and it returns the Creatica generate operation with its input schema. Load the schema and execute POST /v1/generate with a seed and colours. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Creatica Backgrounds API?
Yes. Most operations are read-only catalogue and schema lookups, so a rule can allow just those plus the generate call the agent needs. You choose the operations it may use, so it renders backgrounds and reads structures and nothing more. Each call runs through your own instance and is logged.
For Agents
Generate deterministic procedural SVG and PNG backgrounds from 59 structures and curated palettes, read each structure's parameter schema, and rank structures for a brief. An optional bearer token authenticates calls across 9 operations.
Use for: List the available background structures, Get the parameter schema for a specific structure, Find a structure that matches a natural-language brief, Render a PNG background from a structure and seed
Not supported: Does not handle photo editing, raster upload transforms, or text-to-photo generation. Use for rendering deterministic procedural SVG and PNG backgrounds only.
The Creatica Backgrounds API generates deterministic procedural SVG and PNG backgrounds on demand from 59 structure generators and curated palettes. The same structure, options, and seed always render the same image, and each structure publishes a machine-readable parameter schema and a style card so a caller can build a valid generate request. It also ranks structures for a natural-language brief and serves cacheable image URLs with width, seed, and colour options.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>