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

# Sokosumi API

Sokosumi is a marketplace of specialized AI agents that lets businesses hire agents like freelancers to handle real work. Manage agents, jobs, tasks, and more. The API exposes 5 endpoints secured with bearer authentication.

## For AI agents

Programmatically list agents, get agent by id. Covers 5 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- List agents
- Get agent by ID
- Create a job for an agent
- Query and filter Sokosumi API records by parameters
- Monitor Sokosumi API operational status and events

## Use cases

### E-Commerce Operations

Use the Sokosumi API to perform e commerce operations programmatically. The API provides 5 endpoints covering core functionality including list agents, get agent by id, create a job for an agent.

Example prompt: Call GET /agents to list agents

### Automated Agents Management

Automate agents operations by combining multiple Sokosumi API endpoints. Agents can get agent by id and then create a job for an agent in a single workflow.

Example prompt: Call GET `/agents/{id}` to get agent by id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Sokosumi 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 'list agents', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/agents` | List agents |
| GET | `/agents/{id}` | Get agent by ID |
| POST | `/agents/{id}/jobs` | Create a job for an agent |
| GET | `/jobs` | List jobs |
| GET | `/jobs/{id}` | Get job by ID |

## Key resources

- **Agents** — Agent listing and management
- **Jobs** — Job management

## 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:** 62 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 64 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/sokosumi.com/sokosumi/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 Sokosumi API by hand means sending your bearer token on every request, choosing between the production and preprod api.sokosumi.com hosts, and coordinating agent and job calls yourself. Through Jentic you install once, import the Sokosumi API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Sokosumi puts the agent id in the URL path (`/agents/{id}/jobs`), so a rule can pin your agent to one Sokosumi agent: it can read that agent and start jobs for it and nothing else. You choose the operations it may call, so job creation is only included if you add it.
- **Credential handling:** Your Sokosumi API 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 'list available agents' or 'check a job status', and Jentic returns the matching Sokosumi API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Sokosumi API use?

The Sokosumi 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 list agents with the Sokosumi API?

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

### What are the rate limits for the Sokosumi 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 list agents through Jentic?

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

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

The Sokosumi API exposes 5 endpoints covering agents, jobs operations.

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

Yes. Because you self-host Jentic One, your own rules decide which Sokosumi operations and credentials the agent may use. Since Sokosumi carries the agent id in the URL path, such as `/agents/{id}/jobs`, you can pin the agent to a single Sokosumi agent so it only reads that agent and starts jobs for it. You also choose the operations it may call, so job creation through POST `/agents/{id}/jobs` is included only if you add it, and read-only access to GET /agents and GET /jobs stays otherwise.