Install Jentic One Beta

Connect the Puppet HTTP API to your agent

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

Compile and retrieve a catalog for a node

Retrieve a cached catalog for a node

Store facts for a node

Submit a report for a node

Upload a file to the file bucket

GET STARTED

Start building with Puppet HTTP API

Explore with Jentic One

View OpenAPI Document

Automated Puppet Management

Automate puppet operations by combining multiple Puppet HTTP API endpoints. Agents can retrieve a cached catalog for a node and then retrieve node information in a single workflow.

Call GET /puppet/v3/catalog/{nodename} to retrieve a cached catalog for a node, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Puppet HTTP API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle mutualTLS tokens manually.

Search Jentic for 'compile and retrieve a catalog for a node', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

11 endpoints — puppet server http api for managing catalogs, nodes, facts, reports, file content, file metadata, environments, and file bucket operations.

METHOD

PATH

DESCRIPTION

POST

/puppet/v3/catalog/{nodename}

Compile and retrieve a catalog for a node

GET

/puppet/v3/catalog/{nodename}

Retrieve a cached catalog for a node

GET

/puppet/v3/node/{certname}

Retrieve node information

PUT

/puppet/v3/facts/{nodename}

Store facts for a node

PUT

/puppet/v3/report/{nodename}

Submit a report for a node

GET

/puppet/v3/file_bucket_file/{md5}

Retrieve a file from the file bucket by MD5 hash

PUT

/puppet/v3/file_bucket_file/{md5}

Upload a file to the file bucket

GET

/puppet/v3/file_content/{mount}/{path}

Retrieve file content from the Puppet file server

POST

/puppet/v3/catalog/{nodename}

Compile and retrieve a catalog for a node

GET

/puppet/v3/catalog/{nodename}

Retrieve a cached catalog for a node

GET

/puppet/v3/node/{certname}

Retrieve node information

PUT

/puppet/v3/facts/{nodename}

Store facts for a node

PUT

/puppet/v3/report/{nodename}

Submit a report for a node

GET

/puppet/v3/file_bucket_file/{md5}

Retrieve a file from the file bucket by MD5 hash

PUT

/puppet/v3/file_bucket_file/{md5}

Upload a file to the file bucket

GET

/puppet/v3/file_content/{mount}/{path}

Why Jentic?

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

Setup

Wiring the Puppet HTTP API by hand means provisioning mutual TLS client certificates, pointing at your own Puppet server host and port, and handling catalog and report calls yourself. Through Jentic you install once, import the Puppet HTTP API from the API Directory, store the client certificate once, and your agent calls it.

Permission scoping

Puppet puts the node name in the URL path (/puppet/v3/catalog/{nodename}, /puppet/v3/node/{certname}), so a rule can pin your agent to one node: it can compile a catalog or read facts for that node and nothing else. You choose the operations it may call, so writes like submitting facts or reports are not included unless you add them.

Credential isolation

Your Puppet client certificate 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 'compile a catalog for a node' or 'read a node's facts', and Jentic returns the matching Puppet 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.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Puppet HTTP API through Jentic.

What authentication does the Puppet HTTP API use?

The Puppet HTTP API uses mutualTLS authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I compile and retrieve a catalog for a node with the Puppet HTTP API?

Yes. Use the POST /puppet/v3/catalog/{nodename} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Puppet HTTP API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I compile and retrieve a catalog for a node through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'compile and retrieve a catalog for a node'. Jentic returns the matching Puppet HTTP API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Puppet HTTP API have?

The Puppet HTTP API exposes 11 endpoints covering puppet operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Puppet operations and credentials the agent may use. Since Puppet puts the node name in the URL path, such as /puppet/v3/catalog/{nodename} and /puppet/v3/node/{certname}, you can pin the agent to a single node so it only compiles a catalog or reads facts for that node and nothing else. You choose the operations it may call, so write actions like submitting facts to /puppet/v3/facts/{nodename} or reports to /puppet/v3/report/{nodename} are excluded unless you add them.

Puppet HTTP API

Name: Puppet HTTP API
Brand: Puppet HTTP API
Availability: InStock

Official vendor OpenAPI document · agent-readyE CommerceStorefrontmutualTLS11 EndpointsREST

For Agents

Programmatically compile and retrieve a catalog for a node, retrieve a cached catalog for a node. Covers 11 operations with mutualTLS authentication.

Use for: I need to compile and retrieve a catalog for a node, I want to a cached catalog for a node, Search for node information, Find all store facts for a node

Not supported: Does not handle payments, communications, or crm - use for e-commerce only.

Puppet Server HTTP API for managing catalogs, nodes, facts, reports, file content, file metadata, environments, and file bucket operations. The API exposes 11 endpoints secured with mutualTLS authentication.

Jentic One on Github View OpenAPI Document

Connect the Puppet HTTP API to your agent

Capabilities

Start building with Puppet HTTP API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Puppet HTTP API