canonical: https://jentic.com/apis/speria.jp/speria-jp

# Speria Jp Speria Public API

Speria API for audio source management. Upload audio files, import from URLs, and retrieve shop information. The API exposes 4 endpoints secured with bearer authentication.

## For AI agents

Programmatically get signed url for audio upload, notify audio upload completion. Covers 4 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- Get signed URL for audio upload
- Notify audio upload completion
- Import audio from URL
- Query and filter Speria Public API records by parameters
- Monitor Speria Public API operational status and events

## Use cases

### Storage and Databases Operations

Use the Speria Public API to perform storage operations programmatically. The API provides 4 endpoints covering core functionality including get signed url for audio upload, notify audio upload completion, import audio from url.

Example prompt: Call POST `/v1/audio_sources/upload_url` to get signed url for audio upload

### Automated Audio Sources Management

Automate audio sources operations by combining multiple Speria Public API endpoints. Agents can notify audio upload completion and then import audio from url in a single workflow.

Example prompt: Call POST `/v1/audio_sources/complete` to notify audio upload completion, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Speria Public 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 'get signed url for audio upload', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/audio_sources/upload_url` | Get signed URL for audio upload |
| POST | `/v1/audio_sources/complete` | Notify audio upload completion |
| POST | `/v1/audio_sources/import` | Import audio from URL |
| GET | `/v1/shop` | Get shop information |

## Key resources

- **Audio Sources** — Operations related to Audio Sources
- **Shop** — Operations related to Shop

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/speria.jp/speria-jp/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 the Speria Public API by hand means carrying its bearer token on every request and coordinating the audio-source upload-url, complete, and import steps yourself. Through Jentic you install once, import the Speria Public API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Speria targets travel in the request body, not a resource path, so limit the agent to the operations it needs, such as requesting an upload url or completing an audio-source import. You choose the operations it may call, so it only does what you allow and nothing more.
- **Credential handling:** Your Speria bearer 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.
- **Discovery method:** Agents search Jentic by intent such as 'get a signed url for audio upload' or 'complete an audio import', and Jentic returns the matching Speria operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Amazonaws** — Complementary storage API

## FAQ

### What authentication does the Speria Public API use?

The Speria Public 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 get signed url for audio upload with the Speria Public API?

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

### What are the rate limits for the Speria Public 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 get signed url for audio upload through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get signed url for audio upload'. Jentic returns the matching Speria Public API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Speria Public API have?

The Speria Public API exposes 4 endpoints covering audio sources, shop operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Speria operations and credentials the agent may use. Since Speria targets its audio sources through the request body rather than a resource path, you scope the agent by the operations you grant, for example allowing it to request an upload URL and complete an upload while withholding import from URL or the shop lookup. The agent can only call the operations you permit with the bearer token you store, and nothing else.