Resmo API
✓ Official Vendor SpecCommunicationsPush Notificationsbearer37 EndpointsREST
For Agents
Programmatically execute sql query, list resources. Covers 37 operations with bearer authentication.
Use for: I need to execute sql query, I want to resources, Search for resources by type, Find all resource
Not supported: Does not handle payments, crm, or developer tools — use for communications only.
Resmo is a cloud-native asset visibility and security platform. The Resmo API enables querying your cloud asset inventory, managing integrations, rules, notifications, and audit logs programmatically. Resmo uses SQL-like queries to search across all integrated cloud resources. The API exposes 37 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Resmo API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Resmo 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Resmo API.
Execute SQL query
List resources
Get resources by type
Create integration
Monitor Resmo API operational status and events
Use Cases
Patterns agents use Resmo API for, with concrete tasks.
★ Communications Operations
Use the Resmo API to perform communications operations programmatically. The API provides 37 endpoints covering core functionality including execute sql query, list resources, get resources by type.
Call POST /api/query to execute sql query
Automated ApiKeys Management
Automate apikeys operations by combining multiple Resmo API endpoints. Agents can list resources and then get resources by type in a single workflow.
Call GET /api/resources to list resources, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Resmo 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 'execute sql query', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
37 endpoints — resmo is a cloud-native asset visibility and security platform.
METHOD
PATH
DESCRIPTION
POST
/api/query
Execute SQL query
GET
/api/resources
List resources
GET
/api/resources/{resourceType}
Get resources by type
GET
/api/resources/{resourceType}/{resourceId}
Get resource
POST
/api/integrations
Create integration
GET
/api/integrations
List integrations
GET
/api/integrations/{integrationId}
Get integration
PUT
/api/integrations/{integrationId}
Update integration
POST
/api/query
Execute SQL query
GET
/api/resources
List resources
GET
/api/resources/{resourceType}
Get resources by type
GET
/api/resources/{resourceType}/{resourceId}
Get resource
POST
/api/integrations
Create integration
GET
/api/integrations
List integrations
GET
/api/integrations/{integrationId}
Get integration
PUT
/api/integrations/{integrationId}
Update integration
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Resmo 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., 'execute sql query') and Jentic returns the matching Resmo API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Resmo API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Resmo API through Jentic.
What authentication does the Resmo API use?
The Resmo 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 execute sql query with the Resmo API?
Yes. Use the POST /api/query endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Resmo 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 execute sql query through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'execute sql query'. Jentic returns the matching Resmo API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Resmo API have?
The Resmo API exposes 37 endpoints covering apikeys, auditlogs, changes operations.
GET STARTED