Install Jentic One Beta

Connect the Numonic API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Numonic 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%2Fnumonic.ai%2Fnumonic" | 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%2Fnumonic.ai%2Fnumonic" | 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 Numonic API.

Search creative assets in exact, fuzzy, fulltext, boolean, or smart mode, or by semantic vector similarity

Group assets into nested collections and publish a collection as a public gallery with a share, portfolio, client, or archive preset

Trace an asset's lineage, cross-tool lineage, and Midjourney evolution chain, and read its EXIF technical metadata

Generate and read C2PA provenance manifests for an asset

GET STARTED

Start building with Numonic API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Numonic API for, with concrete tasks.

★ Creative asset librarian agent

A design team's AI agent answers requests like 'find the hero images from the spring shoot' without anyone browsing folders. Through Jentic the agent searches for 'search creative assets', gets the Numonic search operation with its input schema, and sends a query with mode set to smart or fulltext plus filters. For look-alike requests it calls the semantic search operation instead, and the x-api-key is attached at call time.

Call POST /api/v1/assets/search with query 'spring shoot hero', mode smart, and limit 20, then call POST /api/v1/assets/thumbnail-urls with the returned assetIds and present the thumbnails

Client gallery publishing

An agency shares selected work with a client without exposing internal metadata. It creates a collection, adds assets to it by assetH, and publishes it as a public gallery with the client preset, which keeps disclosed metadata minimal. GET /api/v1/collections/{collectionH}/publication reports the publication status, and unpublishing is a single DELETE.

Call POST /api/v1/collections with name 'acme-review', add each asset with POST /api/v1/collections/{collectionH}/assets using its assetH, then call POST /api/v1/collections/{collectionH}/publish with privacyPreset client

AI-generation provenance and C2PA

Teams publishing AI-generated work need to show how it was made. Numonic returns an asset's lineage and cross-tool lineage, the Midjourney evolution chain, and the ComfyUI workflow metadata, and it can generate a C2PA manifest for the asset. That gives reviewers and downstream platforms a verifiable record of the source and edits.

Call GET /api/v1/assets/{assetH}/lineage and GET /api/v1/assets/{assetH}/workflow-metadata for an asset, then call POST /api/v1/assets/{assetH}/c2pa to generate its manifest and GET /api/v1/assets/{assetH}/c2pa to read it back

Review queue and event-driven automation

A studio routes finished assets through approval and reacts to library changes. Assets go into the production review queue with POST /api/v1/production-review/submissions, where reviewers add comments and record decisions. Webhooks registered for events such as asset.created and asset.updated notify other systems, and the HMAC signing secret can be rotated on demand.

Call POST /api/v1/webhooks with name 'library-sync', url https://example.com/hooks/numonic, and events asset.created and asset.updated, then call POST /api/v1/webhooks/{id}/test to send a test event

Key Endpoints

123 endpoints — the numonic api stores, searches, and organizes creative assets such as images, video, audio, and 3d models, and records where each one came from.

METHOD

PATH

DESCRIPTION

POST

/api/v1/assets/search

Search assets

POST

/api/v1/assets/search-semantic

Semantic vector search

GET

/api/v1/assets/{assetH}

Get asset details

POST

/api/v1/collections

Create a collection

POST

/api/v1/collections/{collectionH}/publish

Publish a collection

GET

/api/v1/assets/{assetH}/lineage

Get asset lineage

POST

/api/v1/assets/{assetH}/c2pa

Generate C2PA manifest

POST

/api/v1/webhooks

POST

/api/v1/assets/search

Search assets

POST

/api/v1/assets/search-semantic

Semantic vector search

GET

/api/v1/assets/{assetH}

Get asset details

POST

/api/v1/collections

Create a collection

POST

/api/v1/collections/{collectionH}/publish

Publish a collection

GET

/api/v1/assets/{assetH}/lineage

Get asset lineage

POST

/api/v1/assets/{assetH}/c2pa

Generate C2PA manifest

POST

/api/v1/webhooks

Why Jentic?

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

Setup

Wiring Numonic by hand means sending the napi_ key in x-api-key, passing X-Tenant-ID on multi-tenant keys, addressing assets and collections by 40-character hashes, and picking the right search variant. Through Jentic you install once, import Numonic from the API Directory, store the key once, and your agent calls it.

Permission scoping

Numonic puts the collection hash in the URL path (/api/v1/collections/{collectionH}/...), so a rule can pin your agent to one collection and the operations you pick. You choose the operations it may call, so destructive ones like bulk-delete or webhook deletion are not included unless you add them.

Credential isolation

Your Numonic API key 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 creative assets' or 'generate a C2PA manifest', and Jentic returns the matching Numonic operation with its input schema, so the agent picks the right one of the asset, collection, and provenance operations without browsing the reference docs.

FAQs

Specific to using Numonic API through Jentic.

What authentication does the Numonic API use?

Per its OpenAPI spec, the Numonic API authenticates with an API key prefixed napi_, sent in the x-api-key header and generated in the Numonic dashboard under Settings, API Keys. A key with access to several tenants can pass X-Tenant-ID to pick one. The health checks and the public gallery endpoints are open and need no key. Through Jentic the key is held by your own instance and injected at call time.

Can I search Numonic assets by visual similarity?

Yes. POST /api/v1/assets/search-semantic runs semantic vector search from a required query, and POST /api/v1/assets/search accepts a similarToAssetH or queryVector alongside its other options. The standard search also supports exact, partial, fuzzy, fulltext, boolean, and smart modes, with facets from POST /api/v1/assets/facets.

What are the rate limits for the Numonic API?

The OpenAPI spec does not state numeric request limits for the API. Check the Numonic API documentation at https://numonic.ai/docs/api for current limits.

Does the Numonic API support C2PA content credentials?

Yes. POST /api/v1/assets/{assetH}/c2pa generates a C2PA manifest for an asset and GET /api/v1/assets/{assetH}/c2pa returns it. You can also record a provenance assertion with POST /api/v1/assets/{assetH}/provenance and read lineage for the same asset.

How do I publish a collection as a gallery through Jentic?

Search Jentic for 'publish a collection as a gallery', load the Numonic publish operation, and call POST /api/v1/collections/{collectionH}/publish with a privacyPreset such as client or portfolio. Check the result with GET /api/v1/collections/{collectionH}/publication. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Numonic MCP server?

You do not need an MCP server to give your agent Numonic. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the asset, collection, and provenance operations it needs on demand.

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

Yes. For a search assistant, write a rule that allows POST /api/v1/assets/search, POST /api/v1/assets/search-semantic, and GET /api/v1/assets/{assetH}, so it can find and inspect assets but cannot run bulk deletes, publish galleries, or change webhooks. The calls it makes are logged for review.

Numonic API

AI ReadinessFoundational (D+)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageObject StorageapiKey123 EndpointsREST

For Agents

Search and organize creative assets in Numonic, group them into collections and publish galleries, trace AI-generation lineage and C2PA provenance, and run review, webhook, and automation workflows.

Use for: Find images similar to this asset, Search my assets for product shots tagged summer campaign, Publish this collection as a client gallery, Show the generation lineage for an AI image

Not supported: Does not generate images or video, transcode media, or deliver assets through a CDN. Use for storing, searching, organizing, publishing, and tracing the provenance of creative assets only.

The Numonic API stores, searches, and organizes creative assets such as images, video, audio, and 3D models, and records where each one came from. Assets can be created from a storage path, imported from ComfyUI, tagged in bulk, grouped into nested collections, and published as public galleries with a metadata disclosure preset. Search runs in modes from exact and fuzzy to full-text and semantic vector search, with facets and autocomplete suggestions. Provenance features return an asset's lineage, cross-tool lineage, Midjourney evolution chain, and EXIF metadata, and generate C2PA manifests, alongside webhooks, automation rules, pipelines, prompt libraries, and a production review queue.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

95%

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).

75%

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.

46%

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: FSignals: 4

36%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

78%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

72%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Numonic API to your agent

Capabilities

Start building with Numonic API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Numonic API

Jentic AI Readiness Score

Numonic 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