canonical: https://jentic.com/apis/eongroup.co/eongroup # Eongroup EON API - Documentation Device The EON API manages a connected graph of assets, facilities, products, materials, and items on the EON Group platform, together with the folders and documents attached to them. Your agent creates and retrieves assets by id, internal id, or content hash, runs OCR to extract text from an asset, and organises assets into folders for download. It also records interactions against entities and administers facilities, policies, and labels so an automation can keep a large asset catalogue current. ## For AI agents Manage assets, facilities, products, and materials on the EON platform: create and retrieve records, run OCR on assets, organise folders, and record interactions against entities. ## Scope Does not handle e-commerce checkout, payment processing, or shipping. Use for managing assets, facilities, and their documentation records only. ## Capabilities - Create and retrieve assets by id, internal id, or content hash - Run OCR on an asset to extract its text content - Organise assets into folders and prepare them for download - Manage facilities and associate assets with a facility - Catalog products, materials, and items as structured records - Record and aggregate interactions logged against entities ## Use cases ### Agent-Driven Asset Intake An AI agent connected through Jentic ingests new assets by creating an asset record, running OCR to pull its text, and filing it into a folder. Because EON exposes retrieval by id, internal id, and content hash, the agent can de-duplicate against an existing asset before creating a new one, keeping the catalogue clean. Example prompt: Create an asset, run OCR on it to extract text, and file it into a folder ### Facility Asset Tracking A facilities team tracks which assets belong where by associating assets with facilities and listing a facility's assets. The EON API manages facilities and the asset associations behind them, so an agent reconciles a facility's expected assets against what is actually recorded. Example prompt: List the assets associated with a facility and flag any expected asset that is missing ### Product and Materials Cataloguing A product data team keeps a catalogue of products, materials, and items current. The EON API creates and lists these records and the policies and labels tied to them, letting an agent add a new product with its materials and confirm it was recorded correctly. Example prompt: Create a product, add its materials, and confirm both records resolve on retrieval ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v2/assets/` | List assets | | POST | `/api/v2/assets/` | Create an asset | | GET | `/api/v2/assets/{id}/` | Retrieve an asset by id | | POST | `/api/v2/assets/{id}/ocr/` | Run OCR on an asset | | GET | `/api/v2/facilities/` | List facilities | | GET | `/api/v2/folders/` | List folders | | GET | `/api/v2/products/` | List products | | GET | `/api/v2/interactions/` | List interactions | ## Key resources - **Assets** — Create, retrieve by id or hash, OCR, and relate assets - **Facilities** — Manage facilities and associate assets with them - **Folders** — Organise assets into folders and download them - **Products and materials** — Catalogue products, materials, and items - **Interactions** — Record and aggregate interactions against entities - **Policies and labels** — Manage policies and labels tied to records ## AI readiness 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. - **Score:** 38 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 57 / 100 - Developer Experience & Jentic Compatibility: 55 / 100 - AI-Readiness & Agent Experience: 22 / 100 - Agent Usability: 47 / 100 - Security: 50 / 100 - AI Discoverability: 48 / 100 - **View full report:** https://jentic.com/apis/eongroup.co/eongroup/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the EON API by hand means setting both the `Device-Api-Key` and `Api-Secret` headers correctly and finding the right operation among 192 across assets, facilities, products, and materials. Through Jentic you install once, import the EON API from the API Directory, store the keys once, and your agent calls the operations it needs. - **Permission scoping:** EON puts the asset and facility id in the URL path, so a rule can scope your agent to the operations on one asset or facility. You choose the operations it may call, so destructive ones like asset deletion are not included unless you add them. - **Credential handling:** Your EON API keys are held by your own Jentic One instance, encrypted, and injected into the request headers at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an asset' or 'run OCR on an asset', and Jentic returns the matching EON operation with its input schema so the agent calls the right endpoint without scanning the full list. ## Related APIs - **Contentful API** — A headless platform for structured content and assets, an alternative when the records are editorial rather than physical assets. - **Cloudinary Upload API** — Media upload and transformation that complements EON when assets are images or video needing processing. - **Contentstack Content Delivery API** — A content delivery layer that pairs with EON for publishing managed records to front ends. ## FAQ ### What authentication does the EON API use? The EON API declares two API key headers in its OpenAPI spec: `Device-Api-Key` on almost every operation and `Api-Secret` on the event-handling operation. Through Jentic these keys are held by your own Jentic One instance and attached at execution time, so they never appear in your agent's prompt or logs. ### Can I run OCR on an asset with the EON API? Yes. The asset OCR operation extracts text from an asset you have created, and assets can be retrieved by id, internal id, or content hash. Your agent can create an asset, run OCR to pull its text, and file the result into a folder. ### What are the rate limits for the EON API? The OpenAPI spec does not specify rate limits. Check with EON Group technical support at https://www.eon.xyz/support for the current limits before running high-volume asset operations. ### Is there an EON MCP server? You do not need an MCP server to give your agent the EON API. Jentic connects it directly from the API Directory: import it, store your keys once, and your agent discovers the asset, facility, and product operations it needs on demand without loading an extra server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the EON API? Yes. Write a rule that allows only the read operations your agent needs, such as listing assets and facilities, so it can browse the catalogue but cannot create or delete records across the 192-operation surface, and every call it makes is logged. ### How do I manage EON assets through Jentic? Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the EON API from the Jentic directory and search by intent such as 'create an asset and run OCR'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.