Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gringo Funnels 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%2Fgringofunnels.com%2Fgringofunnels" | shStep 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%2Fgringofunnels.com%2Fgringofunnels" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Gringo Funnels API.
Create publishing Sites and mount funnels, listicles, quizzes, or pages
Connect custom domains and recheck their DNS and TLS state
Declare an immutable deployment bundle and upload its predeclared files
Run quality gates and publish a funnel bundle
Capture and list leads for a funnel
GET STARTED
Reorder or unmount funnels on a Site
Patterns agents use Gringo Funnels API for, with concrete tasks.
★ Agent-published funnels
An AI agent can stand up a marketing funnel through Gringo Funnels by creating a Site, mounting a funnel, connecting a custom domain, and publishing a deployment bundle once its quality gates pass. Each deployment is an immutable bundle with predeclared files, so publishing is reproducible. Connected through Jentic, the agent calls only the site and deployment operations it needs.
Create a Site, mount a funnel, connect a custom domain, and publish a deployment bundle after its quality gates pass
Custom domain onboarding
Publishers need customer-owned domains live with valid TLS. Gringo Funnels connects an external hostname through Cloudflare for SaaS, starts a one-time hostname claim, and rechecks DNS ownership and certificate state. An agent can drive the claim and poll the recheck until the domain is verified.
Start a custom hostname claim for a Site and recheck its DNS and TLS state until it is verified
Lead capture
Funnels exist to collect leads, and those leads need to flow into downstream systems. Gringo Funnels captures a real lead and lists the leads collected, so an agent can pull new leads and forward them to a CRM or email tool. This keeps the funnel's output moving without manual export.
Capture a new lead from a funnel and list the leads collected since the last run
26 endpoints — the gringo funnels api publishes tenant-scoped sites that organize one hostname namespace with mounted funnels, listicles, quizzes, and pages.
METHOD
PATH
DESCRIPTION
/sites
Create an empty publishing Site
/sites/{siteId}/mounts
Mount a funnel, listicle, quiz, or page
/sites/{siteId}/domains
Start a custom hostname claim for a Site
/funnels/{funnelId}/deployments
Declare an immutable bundle inventory
/funnels/{funnelId}/deployments/{deploymentId}/complete
Run quality gates and publish the bundle
/leads
Create a real lead
/leads
List leads
/sites
Create an empty publishing Site
/sites/{siteId}/mounts
Mount a funnel, listicle, quiz, or page
/sites/{siteId}/domains
Start a custom hostname claim for a Site
/funnels/{funnelId}/deployments
Declare an immutable bundle inventory
/funnels/{funnelId}/deployments/{deploymentId}/complete
Run quality gates and publish the bundle
/leads
Create a real lead
/leads
List leads
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Gringo Funnels by hand means handling its Bearer API key, the Cloudflare for SaaS domain claims, and the predeclared-file length and checksum rules on each deployment yourself. Through Jentic you install once, import Gringo Funnels from the API Directory, store the key once, and your agent calls it.
Permission scoping
Gringo Funnels puts the site id in the URL path (/sites/{siteId}/...), so a rule can pin your agent to one Site and its mount and domain operations. You choose the operations it may call, so Site deletion is not included unless you add it.
Credential isolation
Your Gringo Funnels key 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 'publish a funnel' or 'connect a custom domain', and Jentic returns the matching Gringo Funnels operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Gringo Funnels API through Jentic.
What authentication does the Gringo Funnels API use?
Gringo Funnels authenticates with a Bearer API key sent in the Authorization header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Can I connect a custom domain with the Gringo Funnels API?
Yes. The domain operations start a custom hostname claim through Cloudflare for SaaS and recheck DNS ownership and certificate state, for both Sites and legacy funnel domains. You can list the current domains and their DNS and TLS status for a Site.
What are the rate limits for the Gringo Funnels API?
The OpenAPI spec does not specify rate limits, and deployment uploads are bounded instead by predeclared file length and checksum. Check https://gringofunnels.com for current limits.
How do I publish a funnel with the Gringo Funnels API through Jentic?
Search Jentic for 'publish a funnel deployment' and it returns the Gringo Funnels deployment operations with their input schemas, so your agent declares the bundle, uploads files, and runs the completion gate. Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import Gringo Funnels from the API Directory, and store your key once. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with Gringo Funnels?
Yes. Scope the agent to one site: Gringo Funnels puts the site id in the URL path (/sites/{siteId}/...), so a rule can let the agent mount funnels and manage domains for that site and touch no other, and every call it makes is logged.
Is there a Gringo Funnels MCP server?
You don't need an MCP server to connect your agent to Gringo Funnels. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers and calls the operations it needs on demand.
For Agents
Lets an AI agent publish Sites, mount funnels and pages, connect custom domains, deploy bundles, and capture leads.
Use for: Create a publishing Site for a new campaign, Mount a funnel onto a Site, Connect a custom domain and recheck its TLS state, I want to publish a funnel deployment bundle
Not supported: Does not handle email sending, payments, or ad buying. Use for publishing funnels, sites, and pages and capturing leads only.
The Gringo Funnels API publishes tenant-scoped Sites that organize one hostname namespace with mounted funnels, listicles, quizzes, and pages. It connects custom domains through Cloudflare for SaaS and rechecks their DNS and TLS state, declares immutable deployment bundles, uploads predeclared files with exact length and checksum, and runs quality gates before publishing. It also captures and lists leads for the published funnels.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>