Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Developer Tools / Apideck / Ecosystem API
Ecosystem API logo

Apideck Ecosystem API

Browse all Apideck APIs
58
AI ReadinessFoundational (C+)58/100
See full scorecard
Official vendor OpenAPI document · agent-readyDeveloper ToolsProject Managementnone12 EndpointsREST

For Agents

Read Apideck-managed integration marketplace data - list ecosystems, categories, collections, products, and individual listings to render an embedded integrations directory.

Use for: Get the full integration listing directory for a specific Apideck ecosystem, List all categories available in our integration marketplace, Find every listing tagged under the CRM category, Retrieve metadata for a single integration listing by ID

Not supported: Does not authenticate users to integrations, execute calls against connectors, or modify listing metadata - use for read-only marketplace catalog data only.

The Apideck Ecosystem API exposes a read-only catalog of integration listings, categories, collections, and products that power Apideck-hosted integration marketplaces. Applications query this API to render an in-product 'integrations' directory without maintaining their own metadata store, including descriptions, logos, and category groupings for each listing. All twelve endpoints are GET operations scoped under a parent ecosystem ID, with listings filterable by category or collection. It is designed for embedded marketplace UIs rather than for connecting to or executing calls against the underlying integrations.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Ecosystem API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ecosystem 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.

1

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%2Fapideck.com%2Fecosystem" | sh
2

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%2Fapideck.com%2Fecosystem" | 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 Ecosystem API.

Retrieve a full ecosystem record including branding and metadata by ecosystem ID

List every integration listing inside an ecosystem with logos, descriptions, and status

Filter listings by category or by curated collection for marketplace browsing

Look up a single listing by ID to render an integration detail page

Walk product groupings to surface multi-app integration bundles

Page through categories to build a navigation tree for an embedded directory

Use Cases

Patterns agents use Ecosystem API for, with concrete tasks.

★ Embedded Integrations Marketplace

Render an in-product integrations marketplace inside a SaaS application without managing logos, descriptions, or category metadata yourself. The Ecosystem API serves listings, categories, and collections from a single Apideck-hosted source so the marketplace stays current as new connectors are published. Read-only access keeps integration time short - a directory page can be wired up in a day against the twelve GET endpoints.

Fetch all listings under category 'crm' from ecosystem 'acme-marketplace' and return name, logo URL, and description for each

Curated Integration Collections

Group related integrations into themed collections (for example 'Sales Stack' or 'Finance Essentials') and surface them on a marketplace homepage. The collections endpoint returns ordered lists of listings curated by the ecosystem owner, so featured groupings can be controlled centrally rather than hard-coded in the front end. Useful for onboarding flows that recommend integrations based on the user's role.

List all collections in ecosystem 'acme-marketplace' and for each collection retrieve its listings sorted by display order

Category Navigation Tree

Build a side-nav category tree for an integrations directory page. The Ecosystem API exposes categories and the listings under each category, allowing front-end code to render filter chips, faceted search, or a hierarchical browse view. Because the data is centrally managed, taxonomy changes propagate without a deploy.

Retrieve all categories for ecosystem 'acme-marketplace' and return a JSON tree of category name, ID, and child listing count

AI Agent Integration Discovery via Jentic

An AI agent uses Jentic to discover and call the Ecosystem API when a user asks 'what integrations does our product support?'. The agent searches Jentic for 'list integration marketplace listings', loads the Ecosystem operation schema, and executes against a specific ecosystem ID. Jentic stores the Apideck Authorization key separately so the raw secret never enters the agent's prompt context.

Through Jentic, search 'list integration marketplace listings', load the GET /ecosystems/{ecosystem_id}/listings operation, and execute it for ecosystem_id 'acme-marketplace'

Key Endpoints

12 endpoints — the apideck ecosystem api exposes a read-only catalog of integration listings, categories, collections, and products that power apideck-hosted integration marketplaces.

METHOD

PATH

DESCRIPTION

GET

/ecosystems/{ecosystem_id}

Get ecosystem record

GET

/ecosystems/{ecosystem_id}/listings

List all listings in an ecosystem

GET

/ecosystems/{ecosystem_id}/listings/{id}

Get a single listing

GET

/ecosystems/{ecosystem_id}/categories

List categories

GET

/ecosystems/{ecosystem_id}/categories/{id}/listings

List listings within a category

GET

/ecosystems/{ecosystem_id}/collections

List curated collections

GET

/ecosystems/{ecosystem_id}/products

List products

GET

/ecosystems/{ecosystem_id}

Get ecosystem record

GET

/ecosystems/{ecosystem_id}/listings

List all listings in an ecosystem

GET

/ecosystems/{ecosystem_id}/listings/{id}

Get a single listing

GET

/ecosystems/{ecosystem_id}/categories

List categories

GET

/ecosystems/{ecosystem_id}/categories/{id}/listings

List listings within a category

GET

/ecosystems/{ecosystem_id}/collections

List curated collections

GET

/ecosystems/{ecosystem_id}/products

List products

Jentic AI Readiness Score

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.

E

Ecosystem API

- Foundational (C+)
58/100
100
Foundational Compliance
59
Developer Experience & Jentic Compatibility
41
AI-Readiness & Agent Experience
94
Agent Usability
100
Security
29
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
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.

59

Developer Experience & Jentic Compatibility

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

Grade: C+Signals: 4
13%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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.

41

AI-Readiness & Agent Experience

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

Grade: D-Signals: 4
16%

Description Coverage

Coverage of descriptions across API elements.

0%

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.

94

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1
100%

Authentication Strength

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

29

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1
29%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

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

Setup

Wiring the Apideck Ecosystem API by hand means learning its marketplace ecosystem, listing, and category shapes and paging the catalogue yourself. Through Jentic you install once, import Apideck Ecosystem from the API Directory, and your agent calls it, no key to manage since this catalog surface is open.

Permission scoping

The Apideck Ecosystem API puts the ecosystem id in the URL path (/ecosystems/{ecosystem_id}/...), so a rule can pin your agent to one ecosystem: it can read that ecosystem's listings and categories and nothing else. This surface is read-only marketplace data, so no listing metadata changes regardless of the operations you allow.

Credential isolation

Any header your Jentic One instance stores for this API is kept encrypted and injected at execution time. Nothing sensitive enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list marketplace listings' or 'browse ecosystem categories', and Jentic returns the matching Apideck Ecosystem operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Apideck Vault API

→

Once a user picks a listing from the Ecosystem catalog, Vault handles the OAuth flow and stores the resulting connection.

Choose Vault when the agent needs to actually connect a user to an integration after they've browsed the Ecosystem catalog.

Complementary

Apideck Proxy API

→

After Ecosystem surfaces a listing and Vault stores the connection, Proxy forwards arbitrary requests to that connector.

Use Proxy when an agent needs to call an endpoint on a connected integration that isn't covered by an Apideck Unified API.

Alternative

Pipedream API

→

Pipedream offers a competing integrations directory with thousands of pre-built apps and workflow execution.

Choose Pipedream when the agent needs both a marketplace and runtime workflow execution; choose Apideck Ecosystem when only directory metadata is needed.

FAQs

Specific to using Ecosystem API through Jentic.

What authentication does the Apideck Ecosystem API use?

The Ecosystem API spec does not declare a security scheme - listings, categories, and collections are read as marketplace metadata. When called through Jentic, any required Apideck Authorization header value is stored in your Jentic One instance and injected at execution time, so the agent never sees the raw key.

Can I list all integrations in a specific category with the Ecosystem API?

Yes. Call GET /ecosystems/{ecosystem_id}/categories/{id}/listings to retrieve every listing tagged under a category. Use GET /ecosystems/{ecosystem_id}/categories first to discover available category IDs.

What are the rate limits for the Apideck Ecosystem API?

The OpenAPI spec does not publish per-endpoint rate limits. Apideck applies platform-wide quotas - see https://developers.apideck.com for the current numbers tied to your plan. Cache responses where possible; ecosystem metadata changes infrequently.

How do I fetch all listings for a marketplace through Jentic?

Install the SDK with `pip install jentic`, then run the search query 'list integration marketplace listings'. Jentic returns the GET /ecosystems/{ecosystem_id}/listings operation; load its schema and execute it with your ecosystem_id.

Does the Ecosystem API let me trigger or call the underlying integrations?

No. The Ecosystem API is read-only and exposes marketplace metadata only. To actually call CRM, HRIS, or accounting integrations, use the corresponding Apideck Unified API (for example apideck.com/crm) or the Proxy API.

What resources can I retrieve through the Ecosystem API?

Five top-level resources: ecosystems, listings, categories, collections, and products. All are accessed via GET - there are no create, update, or delete endpoints in this API.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The Ecosystem API carries the ecosystem ID in the URL path (/ecosystems/{ecosystem_id}/...), so you can pin the agent to a single ecosystem and let it read only that ecosystem's listings, categories, and collections. Every endpoint is a read-only GET, so no matter which operations you allow, the agent cannot create, update, or delete any listing metadata.

GET STARTED

Start building with Ecosystem API

Explore with Jentic One
View OpenAPI Document