Install Jentic One Beta

Connect the Speria Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Speria Public 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.

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%2Fsperia.jp%2Fsperia-jp" | sh

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%2Fsperia.jp%2Fsperia-jp" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Speria Public API.

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

GET STARTED

Start building with Speria Public API

Explore with Jentic One

View OpenAPI Document

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.

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.

Search Jentic for 'get signed url for audio upload', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — speria api for audio source management.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Speria Public API through Jentic.

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.

Speria Jp Speria Public API

Name: Speria Public API
Brand: Speria Public API
Availability: InStock

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageObject Storagebearer4 EndpointsREST

For Agents

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

Use for: I need to signed url for audio upload, I want to notify audio upload completion, Search for import audio from url, Find all shop information

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

36%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Speria Public API to your agent

Capabilities

Start building with Speria Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Speria Jp Speria Public API

Jentic AI Readiness Score

Speria Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness