canonical: https://jentic.com/open-standards our commitment to Open Standards # Built on Open Standards. Never Locked In. The agentic future must be built on shared, open foundations. Jentic is built entirely on open specifications so that your workflows, integrations, and business logic remain portable, interoperable, and fully under your control. Proud member of the OpenAPI Initiative, a Linux Foundation project ![OpenAPI Initiative](/images/open-standards/openapi-logo-1--light.svg)![OpenAPI Initiative](/images/open-standards/openapi-logo-1.svg)![](/images/open-standards/openapi-logo-2.svg)![](/images/open-standards/openapi-logo-3--light.svg)![](/images/open-standards/openapi-logo-3.svg) ![Arazzo](/images/open-standards/arazzo-logo-1.svg)![](/images/open-standards/arazzo-logo-2--light.svg)![](/images/open-standards/arazzo-logo-2.svg) ![Linux Foundation](/images/open-standards/linux-foundation-logo--light.svg)![Linux Foundation](/images/open-standards/linux-foundation-logo.svg) Why It Matters ## Why Open Standards Are Non-Negotiable ![No Vendor Lock-In](/images/open-standards/icon-no-lock-in.svg) ### No Vendor Lock-In Your workflows are stored as open, declarative artifacts. They can be reviewed, versioned, moved, and run anywhere. If you leave Jentic, your workflows leave with you. ![](/images/open-standards/icon-interop-pill-h.svg)![](/images/open-standards/icon-interop-pill-v.svg)![](/images/open-standards/icon-interop-highlight.svg)![](/images/open-standards/icon-interop-centre.svg) ### Interoperability by Default Open standards mean your agentic workflows work across any agent framework, any model provider, and any cloud. You choose the best tools for the job, not the ones a vendor forces on you. ![](/images/open-standards/icon-community-right.svg)![](/images/open-standards/icon-community-left.svg) ### Community-Driven Evolution Standards improve through public scrutiny and real-world use cases, not behind closed doors. By building on open specs, your infrastructure benefits from contributions across the entire ecosystem. How It Works ## Three Layers of Open Infrastructure Each standard serves a distinct purpose in the stack. Together, they form the complete foundation for enterprise AI that is portable, governed, and built to last. ### OpenAPI Every reliable AI integration starts with a clear contract. OpenAPI gives agents and developers a shared, machine-readable language for API operations, parameters, authentication, and responses. Without it, agents are left guessing. With it, discovery, orchestration, and production hardening all accelerate. [Read the OpenAPI specification](https://spec.openapis.org/oas/latest.html) #### How Jentic Uses OpenAPI Jentic uses OpenAPI as the foundation of its entire platform. Our API Scorecard assesses your existing APIs against OpenAPI best practices, scoring them for both developer experience (DX) and agent experience (AX). We then generate prioritized improvement suggestions using the Overlays specification, so your team can make APIs agent-ready without rebuilding from scratch. Open Source ## Jentic Public APIs We believe the agentic knowledge layer should be open, distributed, and community-owned. Jentic Public APIs is our open repository of API documents and Arazzo workflows, covering 1,500+ public SaaS APIs and growing. It's not just a catalog. It's a shared effort to build the declarative, AI-optimized knowledge that agents need to operate reliably across the world's software. Anyone can contribute, fork, and extend it. The technical infrastructure of the internet succeeded because it was built on open standards and shared resources. The agentic layer of computing deserves the same foundation. [![GitHub](/images/open-standards/github-logo--light.svg)![GitHub](/images/open-standards/github-logo.svg)Explore on GitHub](https://github.com/jentic/jentic-public-apis) ![](/images/open-standards/diagram-particle-effect--light.svg)![](/images/open-standards/diagram-particle-effect.svg) ![](/images/open-standards/diagram-particles--light.svg)![](/images/open-standards/diagram-particles.svg) ![](/images/open-standards/diagram-triangle-lines--light.svg)![](/images/open-standards/diagram-triangle-lines.svg) ![](/images/open-standards/diagram-node-outer--light.svg)![](/images/open-standards/diagram-node-outer.svg)![](/images/open-standards/diagram-node-glow--light.svg)![](/images/open-standards/diagram-node-glow.svg)![](/images/open-standards/diagram-node-highlight--light.svg)![](/images/open-standards/diagram-node-highlight.svg) OpenAPI Contract Layer ![](/images/open-standards/diagram-node-outer--light.svg)![](/images/open-standards/diagram-node-outer.svg)![](/images/open-standards/diagram-node-glow--light.svg)![](/images/open-standards/diagram-node-glow.svg)![](/images/open-standards/diagram-node-highlight--light.svg)![](/images/open-standards/diagram-node-highlight.svg) MCP Agent Layer ![](/images/open-standards/diagram-node-outer--light.svg)![](/images/open-standards/diagram-node-outer.svg)![](/images/open-standards/diagram-node-glow--light.svg)![](/images/open-standards/diagram-node-glow.svg)![](/images/open-standards/diagram-node-highlight--light.svg)![](/images/open-standards/diagram-node-highlight.svg) Arazzo Workflow Layer ![](/images/open-standards/diagram-centre-outer--light.svg)![](/images/open-standards/diagram-centre-outer.svg)![](/images/open-standards/diagram-centre-inner--light.svg)![](/images/open-standards/diagram-centre-inner.svg) OPEN STANDARDS PORTABLE INTEROPERABLE GOVERNED ## Our Philosophy > Workflows are strategic assets that should live as open, declarative artifacts that outlast any product or vendor. If a workflow is written down in a clear spec, it can be reviewed, versioned, secured, observed, and moved. If it is trapped in proprietary glue code, it becomes a liability. ![]()![]() GET STARTED ## Ready to Build on Open Standards? Whether you're assessing your API landscape, building agent workflows, or looking to contribute to the open agentic ecosystem, we'd love to talk. [Book a Demo](/contact)