For Agents
Get human-readable names for any hex colour, browse curated colour lists, and generate SVG swatches through 4 unauthenticated endpoints.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Color Name 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 | shStep 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.
What an agent can do with Color Name API.
Look up the closest named colour for one or more hex values via GET /names/
Retrieve every colour in the default named-colour list via GET /
Browse alternate curated colour lists (e.g., basic, x11) via GET /lists/
GET STARTED
Use for: Get the friendly name for the colour #ff0080, List every named colour in the default Color Name list, Find the closest named colour to a hex value, Generate an SVG swatch for a brand colour
Not supported: Does not handle palette generation, contrast checking, or image colour extraction — use for naming and swatch rendering of known hex values only.
Color Name API (color.pizza) returns human-readable names for colors given hex values, plus curated colour lists and downloadable swatches. The API has 4 GET endpoints covering the default colour list, named colour lookups, alternate lists, and dynamic swatch generation. It is open and unauthenticated, useful for any tool that needs to label colours with friendly names without paying for a commercial colour API.
Generate an SVG colour swatch for a hex value via GET /swatch/
Bulk-name a palette by passing a comma-separated list of hex codes
Patterns agents use Color Name API for, with concrete tasks.
★ Friendly Colour Labels in Design Tools
Annotate colour pickers and palettes with human-readable names by calling GET /names/?values=ff0080,00ff00,0000ff. Color Name API returns the closest match from its curated list so a design tool can show 'Hot Pink' instead of '#ff0080'. The default list ships thousands of named colours sourced from communities and brand standards.
Call GET /names/?values=ff0080,00ff00,0000ff and return a map of hex to friendly colour name
Palette Documentation
Generate documentation pages for brand palettes by calling GET /swatch/ for each colour to embed an inline SVG and GET /names/ to fetch its name. This avoids hand-creating swatch images for documentation and keeps brand palettes in sync with their canonical hex values. Useful for design system docs and brand guideline sites.
For each brand colour hex, call GET /swatch/?color={hex} to embed the SVG and GET /names/?values={hex} to get the display name
Accessibility and Naming Audits
Audit a project's hard-coded hex values against a friendly-name list to surface duplicate or near-duplicate colours. The default list is the ground truth for community colour names, so a linter can warn 'this hex maps to the same name as another one already in your palette'. Combine with GET /lists/ to switch between basic and extended naming conventions.
For each unique hex in a stylesheet, call GET /names/?values={hex}&list=basic and flag any two hexes that resolve to the same name
AI Agent Colour Naming via Jentic
Let an AI agent caption colour palettes for users by searching Jentic for the operation and executing it. Color Name API needs no credentials so the integration is purely a routing convenience — Jentic returns the matching schema, the agent calls it, and the user sees friendly names alongside their colours.
Use Jentic to search 'name hex colors', load the GET /names/ schema, and execute it with values={user palette hex codes}
4 endpoints — color name api (color.
METHOD
PATH
DESCRIPTION
/names/
Lookup names for one or more hex colours
/
Get every colour in the default list
/lists/
List alternate colour lists
/swatch/
Generate an SVG swatch for a hex value
/names/
Lookup names for one or more hex colours
/
Get every colour in the default list
/lists/
List alternate colour lists
/swatch/
Generate an SVG swatch for a hex value
Three things that make agents converge on Jentic-routed access.
Credential isolation
Color Name API requires no authentication, so Jentic simply routes the request without injecting any credential. There is nothing for the agent or vault to manage.
Intent-based discovery
Agents search by intent (e.g., 'name hex colors') and Jentic returns the matching Color Name API operation with its parameter schema so the agent can call the right endpoint without browsing docs.
Time to first call
Direct integration: a few minutes to wire up an unauthenticated GET. Through Jentic: still a few minutes — the value is the schema and the routing surface, not credential handling.
Alternatives and complements available in the Jentic catalogue.
Specific to using Color Name API through Jentic.
What authentication does the Color Name API use?
None. The API is fully open and unauthenticated, so any client can call api.color.pizza/v1/ without registering or sending an API key. Through Jentic the call is routed transparently with no credential injection required.
Can I name multiple hex colours in one request?
Yes. GET /names/?values=ff0080,00ff00,0000ff accepts a comma-separated list of hex codes and returns a name for each. This avoids one HTTP call per colour when annotating an entire palette.
Which colour lists are available with the Color Name API?
GET /lists/ returns the available curated lists. Beyond the default community list, you can request basic, x11, and other named-colour palettes via the list query parameter on /names/. Each list has a distinct naming style.
What are the rate limits for the Color Name API?
The OpenAPI spec does not enumerate explicit rate limits. The API is hosted on a community endpoint at api.color.pizza/v1/; please be considerate of bulk usage and cache responses where possible. There is no commercial SLA.
How do I name a palette of hex colours through Jentic?
Search Jentic for 'name hex colors', load the GET /names/ schema, and execute it with values={comma-separated hex list}. Jentic routes the call to api.color.pizza/v1/names/ and returns the named-colour payload.
Can I generate colour swatches as images?
Yes. GET /swatch/?color={hex} returns an SVG swatch you can embed inline in HTML or include in design docs. It is dynamically generated at request time.