Raygun API

Name: Raygun API
Brand: Raygun API
Availability: InStock

✓ Official Vendor SpecIdentity AuthAuthenticationbearer41 EndpointsREST

For Agents

Programmatically list applications, get application by id. Covers 41 operations with bearer authentication.

Install Jentic One Beta

Connect the Raygun API to your agent

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

List applications

Get application by ID

Regenerate API key

Access Raygun API identity auth resources via REST API

GET STARTED

Start building with Raygun API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Raygun API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Raygun API to perform identity auth operations programmatically. The API provides 41 endpoints covering core functionality including list applications, get application by id, get application by API key.

Call GET /applications to list applications

Automated Applications Management

Automate applications operations by combining multiple Raygun API endpoints. Agents can get application by id and then get application by API key in a single workflow.

Call GET /applications/{applicationId} to get application by id, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Raygun 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 bearer tokens manually.

Search Jentic for 'list applications', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

41 endpoints — raygun's api allows you to access your raygun data so that you can display, manipulate and process it in other tools, scripts and applications.

METHOD

PATH

DESCRIPTION

GET

/applications

List applications

GET

/applications/{applicationId}

Get application by ID

GET

/applications/api-key/{apiKey}

Get application by API key

POST

/applications/{applicationId}/regenerate-api-key

Regenerate API key

GET

/plans

Get plans

GET

/teams

List teams

GET

/teams/{teamId}

Get team by ID

GET

/invitations

List invitations

GET

/applications

List applications

GET

/applications/{applicationId}

Get application by ID

GET

/applications/api-key/{apiKey}

Get application by API key

POST

/applications/{applicationId}/regenerate-api-key

Regenerate API key

GET

/plans

Get plans

Why Jentic?

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

Setup

Wiring the Raygun API by hand means setting up its bearer auth against the v3 host, walking the applications, teams, and invitations resources, and handling paging and retries yourself. Through Jentic you install once, import the Raygun API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The Raygun API puts the application id in the URL path (/applications/{applicationId}/...), so a rule can pin your agent to one application. You choose the operations it may call, so a destructive one like regenerate-api-key is not included unless you add it, letting the agent read application and team details without rotating keys.

Credential isolation

Your Raygun API token 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 'list applications' or 'get a team by id', and Jentic returns the matching Raygun API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Raygun API through Jentic.

What authentication does the Raygun API use?

The Raygun API uses a Bearer token in the Authorization header. 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 list applications with the Raygun API?

Yes. Use the GET /applications endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Raygun 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 list applications through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list applications'. Jentic returns the matching Raygun API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Raygun API have?

The Raygun API exposes 41 endpoints covering applications, invitations, plans operations.

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

Yes. Jentic One is self-hosted by you, and your own rules decide which Raygun API operations and credentials the agent may use. Because the API carries the application id in the URL path, such as /applications/{applicationId}, you can pin the agent to a single application and grant read-only calls like list applications, get application by ID, and get a team by ID. A destructive operation such as regenerate-api-key is not available to the agent unless you explicitly add it, so it can inspect application and team details without rotating keys.

Raygun API

Connect the Raygun API to your agent

Capabilities

Start building with Raygun API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs