Install Jentic One Beta

Connect the GrowthHero API to your agent

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

Retrieve a single referral by id to check its current status and attributed campaign

List referrals in the workspace to reconcile against an internal CRM or billing system

Enumerate active campaigns to find the right campaign id before creating a referral

GET STARTED

Start building with GrowthHero API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GrowthHero API for, with concrete tasks.

★ Sign-up referral attribution

Track new sign-ups back to the partner or customer who referred them. When a user completes a SaaS sign-up flow, the backend calls POST /referrals with the referrer code and customer details, and GrowthHero records the attribution against the right campaign. Later, GET /referrals/{id} confirms the status (pending, approved, paid) so finance can reconcile partner payouts. Authentication is a simple X-API-Key header.

Call POST /referrals with the referrer_code and new customer email when a sign-up completes, then poll GET /referrals/{id} weekly until the status reaches paid.

Affiliate program reconciliation

Reconcile GrowthHero affiliate activity against an internal billing database by paging through GET /referrals on a schedule. The data flows into a finance warehouse so analysts can verify commissions match expected payouts and spot referrals stuck in pending status. Pairing this with GET /campaigns lets ops teams confirm each referral was attributed to a still-active campaign before they pay out.

Page through GET /referrals nightly, join the results to the billing table, and flag any referral whose campaign is no longer listed in GET /campaigns.

Campaign-aware in-product referral widgets

Power an in-product referral widget that always shows the right campaign for the current user. The widget calls GET /campaigns at load time, picks the campaign matching the user's plan or geography, and posts new referrals to /referrals when the user shares a link. This avoids the common bug where customers refer friends to a paused campaign and lose attribution.

Call GET /campaigns, pick the campaign matching the customer's tier, and call POST /referrals when the user clicks 'Invite a friend'.

AI agent integration through Jentic

Expose GrowthHero referral and campaign operations to an AI agent through Jentic so growth teams can ask questions like 'how many referrals did campaign X drive last week?' without writing SQL. The agent searches Jentic for the right intent, loads the operation schema, and executes it against api.growthhero.io. Jentic isolates the X-API-Key in its vault, so the agent never sees the raw key.

Through Jentic, search 'list growthhero referrals', load the operation, and execute it for the configured workspace.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for growthhero api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/referrals

List referrals in the workspace

POST

/referrals

Create a new referral

GET

/referrals/{id}

Retrieve a single referral by id

GET

/campaigns

List active campaigns

GET

/campaigns/{id}

Retrieve a single campaign by id

GET

/referrals

List referrals in the workspace

POST

/referrals

Create a new referral

GET

/referrals/{id}

Retrieve a single referral by id

GET

/campaigns

List active campaigns

GET

/campaigns/{id}

Retrieve a single campaign by id

Why Jentic?

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

Setup

Wiring the GrowthHero API by hand means setting the X-API-Key header on every call to api.growthhero.io and handling referral and campaign pagination and retries yourself. Through Jentic you install once, import GrowthHero from the API Directory, store the key once, and your agent calls it.

Permission scoping

GrowthHero puts the referral and campaign id in the URL path (/referrals/{id}, /campaigns/{id}), so a rule can pin your agent to one referral or campaign for reads. You choose the operations it may call, so creating new referrals is not included unless you add it.

Credential isolation

Your GrowthHero X-API-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 'create a GrowthHero referral' or 'list GrowthHero campaigns', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using GrowthHero API through Jentic.

Why is there no official OpenAPI spec for GrowthHero API?

GrowthHero does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call GrowthHero API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the GrowthHero API use?

GrowthHero uses an X-API-Key header on every request. The key is generated in the GrowthHero dashboard and scoped to one workspace. Through Jentic the X-API-Key is stored encrypted in the vault and the agent receives only a scoped Jentic-mediated token.

Can I create a new referral via the API?

Yes. POST /referrals creates a referral attributed to a specified campaign. The endpoint expects the referrer code and new customer details in the request body and returns the created referral id, which can then be polled via GET /referrals/{id}.

What are the rate limits for the GrowthHero API?

The public spec does not document explicit rate limits. GrowthHero throttles at the platform level per workspace; back off on HTTP 429 responses and batch reconciliation jobs into off-peak windows.

How do I list campaigns through Jentic?

Install Jentic with pip install jentic, search for 'list growthhero campaigns', load the matching operation, and execute it. Jentic resolves the call to GET /campaigns and returns the active campaign list with their ids and metadata.

How do I find the campaign a referral was attributed to?

Call GET /referrals/{id} for the referral and read its campaign reference, then call GET /campaigns/{id} to load the full campaign metadata. This pair of calls is enough to reconcile any referral against the program rules in force when it was created.

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

Yes. Because you run Jentic One yourself, your own rules decide which GrowthHero operations the agent may call, so you can grant read-only access to GET /referrals, GET /referrals/{id}, GET /campaigns, and GET /campaigns/{id} while leaving POST /referrals off entirely unless you add it. Since GrowthHero puts the referral and campaign identifier in the URL path, a rule can also pin the agent to a single referral or campaign for reads. Your X-API-Key is stored once by your own instance and injected only when a permitted operation runs, so the agent never handles the raw key.

GrowthHero API

AI ReadinessNon-Ready (F)0/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticMarketingMarketing AutomationapiKey5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create and look up referrals and list active campaigns inside GrowthHero referral and growth-tracking programmes.

Use for: I need to create a new referral for a GrowthHero campaign, List all referrals attributed in our GrowthHero account, Get the status of referral 12345, Retrieve the metadata for a specific GrowthHero campaign

Not supported: Does not handle email marketing campaigns, payment processing, or full affiliate payout disbursement - use for referral creation, lookup, and campaign listing in GrowthHero only.

Jentic publishes the only available OpenAPI specification for GrowthHero API, keeping it validated and agent-ready. GrowthHero is a referral, affiliate, and growth-tracking platform used by SaaS and e-commerce brands to run referral programmes and partner campaigns. The API exposes 5 public endpoints covering referral creation and lookup plus campaign listing and retrieval, authenticated with an X-API-Key header. It is intentionally lightweight: marketers and agents can register a referral, fetch referral status, and inspect which campaigns are active without a heavy SDK.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

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

Grade: CSignals: 4

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.

AI-Readiness & Agent Experience

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

Grade: D+Signals: 4

44%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the GrowthHero API to your agent

Capabilities

Start building with GrowthHero API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

GrowthHero API

Jentic AI Readiness Score

GrowthHero API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness