Timoni
Timoni is a package manager for Kubernetes powered by CUE that provides a type-safe alternative to Helm charts. It enables software vendors to define complex application deployments packaged as Modules using CUE definitions, distributed as OCI artifacts in container registries with semantic versioning and cryptographic signing.
Timoni publishes 2 APIs on the APIs.io network: Artifacts API and Modules API. Tagged areas include Containers, Kubernetes, Package Manager, and CUE.
The Timoni catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.
Timoni’s developer surface includes authentication, documentation, getting-started guide, and 9 more developer resources.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
Timoni Artifacts API
OCI artifact operations for Timoni packages
Timoni Modules API
Timoni module management and distribution
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Timoni Module Registry API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Timoni Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Timoni Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Timoni Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Timoni Context
JSON-LDSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
Timoni API Rules
SPECTRALJSON Schema 1
Standalone JSON Schema definitions for this provider's data models.
Timoni Module
JSON SCHEMAJSON Structure 1
JSON Structure definitions describing this provider's data shapes.
Timoni Module Structure
JSON STRUCTUREExamples 1
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type