Install Jentic One Beta

Connect the Iconfinder API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Iconfinder 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%2Ficonfinder.com%2Ficonfinder" | sh

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%2Ficonfinder.com%2Ficonfinder" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Iconfinder API.

Search across millions of icons by keyword, style, premium status, vector availability, and license type

Retrieve a specific icon's metadata, formats, sizes, and download URL via /icons/{icon_id}

List and inspect iconsets including their author, category, style, and contained icons

Browse curated taxonomy through /categories and /styles to filter results by visual theme

GET STARTED

Start building with Iconfinder API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Iconfinder API for, with concrete tasks.

★ In-App Icon Picker

Embed an icon picker inside a design tool, no-code builder, or CMS so end users can search Iconfinder's library without leaving the product. The /icons/search endpoint accepts a query, style, license, and vector filter, returning paginated results with thumbnail URLs. Most integrations are live within a day because the API returns ready-to-render image URLs.

Call GET /icons/search with query=cart, vector=true, premium=false and return the top 20 icons with their SVG download URLs

Brand Asset Discovery

Surface licensed icons and iconsets for marketing teams building campaign assets. Agents filter /icons/search by style and license, then fetch /licenses/{license_id} to confirm commercial usage rights before download. This avoids the manual step of vetting each asset against legal policy.

Search for flat-style business icons with a commercial license, then call GET /licenses/{license_id} for each result to confirm allowed usage

Iconset Catalog Sync

Mirror a subset of Iconfinder's catalog into an internal asset library. Agents page through /iconsets, fetch /iconsets/{iconset_id}/icons for each set, and persist metadata and download URLs. Useful for teams that need offline access or want to enforce internal tagging on top of vendor data.

List the first 50 iconsets via GET /iconsets, then for each call GET /iconsets/{iconset_id}/icons and store the icon IDs and download URLs

AI Agent Visual Asset Lookup

An AI design assistant uses Jentic to find Iconfinder operations matching a natural-language request like 'a minimal shield icon for a security feature'. Jentic returns the search schema, the agent calls /icons/search with the right parameters, and surfaces results inline in a chat or design canvas without scraping the web.

Use Jentic search query 'find an icon' to load the Iconfinder /icons/search schema, then execute with style=line and query=shield

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for iconfinder api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/icons/search

Search icons by keyword, style, license, and vector availability

GET

/icons/{icon_id}

Retrieve metadata and formats for a specific icon

GET

/icons/{icon_id}/download

Get a download URL for an icon in a specific size or format

GET

/iconsets

List iconsets in the catalog

GET

/iconsets/{iconset_id}/icons

List icons within a specific iconset

GET

/categories

List all categories in the Iconfinder taxonomy

GET

/licenses/{license_id}

Retrieve license terms for an icon

GET

/icons/search

Search icons by keyword, style, license, and vector availability

GET

/icons/{icon_id}

Retrieve metadata and formats for a specific icon

GET

/icons/{icon_id}/download

Get a download URL for an icon in a specific size or format

GET

/iconsets

List iconsets in the catalog

GET

/iconsets/{iconset_id}/icons

List icons within a specific iconset

GET

/categories

List all categories in the Iconfinder taxonomy

GET

/licenses/{license_id}

Retrieve license terms for an icon

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Iconfinder API by hand means handling its bearer-token auth against the v4 host and mapping its icon and iconset search and download routes yourself. Through Jentic you install once, import the Iconfinder API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Iconfinder puts the icon and iconset ids in the URL path (/icons/{icon_id}, /iconsets/{iconset_id}), so a rule can pin your agent to searching, reading, and downloading icons. You choose the operations it may call, so it only touches the read and download endpoints you name.

Credential isolation

Your Iconfinder 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 'search for icons' or 'download an icon by id', and Jentic returns the matching Iconfinder operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Iconfinder API through Jentic.

Why is there no official OpenAPI spec for Iconfinder API?

Iconfinder does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Iconfinder API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Iconfinder API use?

The Iconfinder API uses HTTP bearer authentication. Requests must include an Authorization: Bearer <token> header with an API client token issued from the Iconfinder developer dashboard. Through Jentic, the token is stored encrypted in your Jentic One instance and injected at execution time, so it never enters the agent's prompt context.

Can I download SVG icons through the Iconfinder API?

Yes. After locating an icon via GET /icons/search or GET /icons/{icon_id}, agents can call GET /icons/{icon_id}/download with the desired format and size to receive a download URL. Vector formats are available where the icon's source supports them - filter the search with vector=true to limit results to icons with SVG output.

What are the rate limits for the Iconfinder API?

Iconfinder applies per-account rate limits and a monthly download quota tied to the subscription tier. The OpenAPI spec does not encode the exact limits because they depend on your plan. Check your account dashboard for the current ceiling, and design agents to handle 429 responses with backoff.

How do I search icons through Jentic?

Run pip install jentic and import the SDK, then await client.search('find an icon') to discover Iconfinder operations. Load the /icons/search schema with await client.load and execute with parameters such as query, style, and vector. Run Jentic One, the self-hosted execution layer, for an API key.

Does the Iconfinder API expose license metadata?

Yes. Each icon response includes a license reference, and GET /licenses/{license_id} returns the full license terms including commercial use rights and attribution requirements. Agents should call this endpoint before bulk-downloading premium content to confirm compliance.

Can I limit what my agent is allowed to do with the Iconfinder API?

Yes. Jentic One runs self-hosted, so you set the rules that decide which Iconfinder operations your agent may call and which credentials it may use. Because Iconfinder puts icon and iconset ids in the URL path, you can pin the agent to read-only work such as GET /icons/search, GET /icons/{icon_id}, GET /icons/{icon_id}/download, and GET /licenses/{license_id}, and leave out anything you do not name. You name the exact endpoints, so the agent only searches, reads, and downloads the icons you allow.

Iconfinder API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticMediaImage Processingbearer13 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search and download icons and icon sets from Iconfinder's library, browse by category, style, or author, and retrieve license-aware download links.

Use for: I need to find a free vector icon of a shopping cart, Search for premium iconsets in a flat style for a finance dashboard, Get the SVG download URL for a specific icon ID, List all categories available in the Iconfinder catalog

Not supported: Does not handle photo stock libraries, font hosting, or generative image creation - use for icon and iconset discovery and download only.

Jentic publishes the only available OpenAPI specification for Iconfinder API, keeping it validated and agent-ready. Iconfinder offers programmatic access to a library of over 6 million icons and icon sets across multiple styles and licenses. Through 13 endpoints covering icons, iconsets, categories, styles, authors, licenses, and user accounts, agents can search by keyword and style, retrieve metadata, and request download URLs for raster or vector assets. The API supports filtered search, faceted browsing by style or category, and license-aware delivery for both free and premium icons.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

28%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Iconfinder API to your agent

Capabilities

Start building with Iconfinder API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Iconfinder API

Jentic AI Readiness Score

Iconfinder API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness