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.

Use for: I need to applications, I want to application by id, Search for application by api key, Find all regenerate api key

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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

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?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Raygun API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'list applications') and Jentic returns the matching Raygun API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Raygun API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Raygun API

Connect the Raygun API to your agent

Capabilities

Start building with Raygun API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs