canonical: https://jentic.com/apis/resmo.com/resmo

# Resmo API

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.

## For AI agents

Programmatically execute sql query, list resources. Covers 37 operations with bearer authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Execute SQL query
- List resources
- Get resources by type
- Create integration
- Monitor Resmo API operational status and events

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'execute sql query', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **ApiKeys** — Operations related to ApiKeys
- **AuditLogs** — Operations related to AuditLogs
- **Changes** — Operations related to Changes
- **Integrations** — Operations related to Integrations
- **Notifications** — Operations related to Notifications

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 57 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 62 / 100
- **View full report:** https://jentic.com/apis/resmo.com/resmo/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Resmo by hand means setting its bearer auth on every request against the id.resmo.app host and tracking resource type, resource id, and integration id across query and integration calls yourself. Through Jentic you install once, import the Resmo API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Resmo puts the resource and integration ids in the URL path (`/api/resources/{resourceType}/{resourceId}`), so a rule can pin your agent to reading a specific resource. You choose the operations it may call, so a state-changing one like updating an integration is not included unless you add it.
- **Credential handling:** Your Resmo 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.
- **Discovery method:** Agents search Jentic by intent such as 'run a SQL query' or 'list resources of a type', and Jentic returns the matching Resmo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

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

Yes. Because you run Jentic One yourself, your own rules decide which Resmo operations and credentials the agent may use. Resmo puts the resource and integration ids in the URL path, such as `/api/resources/{resourceType}/{resourceId}`, so you can pin the agent to reading a specific resource type or id. You also choose exactly which operations it may call, so a state-changing endpoint like PUT `/api/integrations/{integrationId}` stays off limits unless you explicitly allow it.