Pyrus API
✓ Official Vendor SpecDeveloper ToolsSource Controlbearer32 EndpointsREST
For Agents
Programmatically authenticate and obtain access token, get a task by id. Covers 32 operations with bearer authentication.
Use for: I need to authenticate and obtain access token, I want to a task by id, Search for a task, Find all a task
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Pyrus is a platform for real-time messaging, task management, and workflow automation. The API allows building highly customized integrations in any programming language. The API exposes 32 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Pyrus API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pyrus 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.
1
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%2Fpyrus.com%2Fpyrus" | sh2
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%2Fpyrus.com%2Fpyrus" | 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.
Capabilities
What an agent can do with Pyrus API.
Authenticate and obtain access token
Get a task by ID
Delete a task
Create a task
Add a comment to a task
List all forms
Use Cases
Patterns agents use Pyrus API for, with concrete tasks.
★ Developer Tools Operations
Use the Pyrus API to perform developer tools operations programmatically. The API provides 32 endpoints covering core functionality including authenticate and obtain access token, get a task by id, delete a task.
Call POST /auth to authenticate and obtain access token
Automated Auth Management
Automate auth operations by combining multiple Pyrus API endpoints. Agents can get a task by id and then delete a task in a single workflow.
Call GET /tasks/{taskId} to get a task by id, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Pyrus 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 'authenticate and obtain access token', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
32 endpoints — pyrus is a platform for real-time messaging, task management, and workflow automation.
METHOD
PATH
DESCRIPTION
POST
/auth
Authenticate and obtain access token
GET
/tasks/{taskId}
Get a task by ID
DELETE
/tasks/{taskId}
Delete a task
POST
/tasks
Create a task
POST
/tasks/{taskId}/comments
Add a comment to a task
GET
/forms
List all forms
GET
/forms/{formId}
Get a form by ID
GET
/forms/{formId}/register
Get form task register
POST
/auth
Authenticate and obtain access token
GET
/tasks/{taskId}
Get a task by ID
DELETE
/tasks/{taskId}
Delete a task
POST
/tasks
Create a task
POST
/tasks/{taskId}/comments
Add a comment to a task
GET
/forms
List all forms
GET
/forms/{formId}
Get a form by ID
GET
/forms/{formId}/register
Get form task register
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Pyrus API by hand means exchanging credentials for a bearer token and handling task, comment, and form calls yourself. Through Jentic you install once, import the Pyrus API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Pyrus puts the task and form ids in the URL path (/tasks/{taskId}, /forms/{formId}), so a rule can pin your agent to one task or form: it can read that task or add a comment and nothing else. You choose the operations it may call, so task deletion is not included unless you add it.
Credential isolation
Your Pyrus 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 'create a task' or 'add a comment to a task', and Jentic returns the matching Pyrus 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
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Pyrus API through Jentic.
What authentication does the Pyrus API use?
The Pyrus 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 authenticate and obtain access token with the Pyrus API?
Yes. Use the POST /auth endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Pyrus 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 authenticate and obtain access token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticate and obtain access token'. Jentic returns the matching Pyrus API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Pyrus API have?
The Pyrus API exposes 32 endpoints covering auth, tasks, forms operations.
GET STARTED