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

# ResourceSpace API

ResourceSpace digital asset management API providing functions for managing resources, collections, metadata, users, and search. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically call an API function via post, call an API function. Covers 2 operations with apiKey authentication.

## Scope

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

## Capabilities

- Call an API function via POST
- Manage developer tools data programmatically
- Integrate ResourceSpace API into automated workflows
- Query and filter ResourceSpace API records by parameters
- Monitor ResourceSpace API operational status and events

## Use cases

### Developer Tools Operations

Use the ResourceSpace API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including call an API function via post, call an API function.

Example prompt: Call POST / to call an API function via post

### Data Retrieval and Monitoring

Query ResourceSpace API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary ResourceSpace API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'call an API function via post', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/` | Call an API function via POST |
| GET | `/` | Call an API function |

## 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:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 15 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/resourcespace.com/resourcespace/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 ResourceSpace by hand means computing the SHA256 signature over the private key and query string for every call, resolving your instance domain, and dispatching each API function yourself. Through Jentic you install once, import the ResourceSpace API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** ResourceSpace routes every request through a single API endpoint and selects the function in the request parameters rather than a resource id in the path, so limit the agent to the specific functions it needs. You choose that set, so a write function is not reachable unless you add it.
- **Credential handling:** Your ResourceSpace private 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 'call an API function via POST', and Jentic returns the matching ResourceSpace operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the ResourceSpace API use?

The ResourceSpace API uses an API key passed in the `sign` query. 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 call an API function via post with the ResourceSpace API?

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

### What are the rate limits for the ResourceSpace 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 call an API function via post through Jentic?

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

### How many endpoints does the ResourceSpace API have?

The ResourceSpace API exposes 2 endpoints for developer tools operations.

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

Yes. Because Jentic One is self-hosted, you define the rules that decide which ResourceSpace functions and credentials your agent may use. ResourceSpace routes every request through a single API endpoint and picks the function from the request parameters rather than a resource id in the path, so you allow only the specific functions the agent needs, such as calling a read-only API function via POST. A write function stays unreachable unless you add it to that set, and your private API key is injected at execution time rather than exposed to the agent.