How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Yutori Browsing API

The Browsing API from Yutori — 3 operation(s) for browsing.

Yutori Browsing API is one of 5 APIs that Yutori publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Browsing. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 4 operations across 3 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api.yutori.com.

4 operations 3 paths 10 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.yutori.com
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Yutori Browsing API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Use Authorization: Bearer

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Browsing 4
POST
/v1/browsing/tasks
Create A Task
agent_run_endpoint_v1_browsing_tasks_post body → 200422
GET
/v1/browsing/tasks
List Tasks
list_browsing_tasks_v1_browsing_tasks_get 3 params → 200422
GET
/v1/browsing/tasks/{id}
Get Agent Run Status
get_agent_run_status_v1_browsing_tasks__id__get 1 param → 200422
GET
/v1/browsing/tasks/{id}/trajectory
Download Task Trajectory
get_task_trajectory_v1_browsing_tasks__id__trajectory_get 2 params → 200422

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are AgentRunRequest (11 properties), AgentRunResponse (9 properties), TaskListResponse (8 properties), TaskListItem (6 properties). Each schema is shown below with its type and property counts.

ValidationError
object
5 properties 3 required
TaskListItem
object
Lightweight one-time task metadata for developer API list endpoints.
6 properties 5 required
JsonSchemaSpec
object
2 properties
AgentRunResponse
object
9 properties 3 required
TaskListResponse
object
8 properties 1 required
HTTPValidationError
object
1 property
RejectionReason
string
TaskSpec
object
1 property
AgentRunRequest
object
11 properties 2 required
TaskListSummary
object
Summary counts of one-time tasks by lightweight list status.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

yutori-browsing-api-openapi.yml Raw ↑

Other APIs Yutori publishes across the network.

Yutori Chat Completions API
Yutori Health API
Yutori Research API
Yutori Scouting API
Where this information came from

This is an independent, third-party profile of Yutori Browsing API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.