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

usestring-ai Builds API

Starting, watching, steering and finishing a feed build.

usestring-ai Builds API is one of 9 APIs that String publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 12 JSON Schema definitions.

Tagged areas include Builds. The published artifact set on APIs.io includes an OpenAPI specification and 12 JSON Schemas.

This API exposes 10 operations across 7 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, /.

10 operations 7 paths 33 schemas 1 DELETE4 GET1 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://request.usestring.ai/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

usestring-ai Builds API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — A Composer API key: Authorization: Bearer skfblive….

Paths & Operations 10

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

Builds 10

Starting, watching, steering and finishing a feed build.

GET
/v1/builds
List builds
listBuilds 2 params → 200400401403429500503504
POST
/v1/builds
Start a build
createBuild body → 201400401403409413429500
DELETE
/v1/builds/{id}
Delete a build
deleteBuild 1 param → 204401403404409429500503
GET
/v1/builds/{id}
Get a build
getBuild 1 param → 200401403404429500503504
PATCH
/v1/builds/{id}
Set auto-proceed
updateBuild 1 param body → 204400401403404409413429
POST
/v1/builds/{id}/cancel
Cancel a build
cancelBuild 1 param body → 204400401403404409413429
GET
/v1/builds/{id}/events
Stream a build (server-sent events)
streamBuild 2 params → 200401403404429500503504
POST
/v1/builds/{id}/gates/{gate_id}
Answer a gate
answerGate 2 params body → 204400401403404409413429
POST
/v1/builds/{id}/messages
Send a message into a build
sendMessage 1 param body → 204400401403404409413429
GET
/v1/builds/{id}/sample
Get a build's sample rows
getSample 1 param → 200401403404429500503504

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are Build (16 properties), BuildSummary (10 properties), Report (9 properties), GateRecord (8 properties). Each schema is shown below with its type and property counts.

BuildList
object
4 properties 3 required
BuildSummary
object
10 properties 4 required
GateRecord
object
8 properties 4 required
SourcePickerAnswer
object
2 properties
SourceCandidate
object
5 properties 2 required
Choice
object
3 properties 1 required
SchemaReviewAnswer
object
3 properties 1 required
Activity
object
4 properties 1 required
QuestionnaireAnswer
object
1 property 1 required
PublishReviewOptions
object
6 properties 2 required
CreateBuildRequest
object
1 property 1 required
Field
object
6 properties 4 required
SchemaColumnEdit
object
4 properties 1 required
Question
object
3 properties 2 required
CancelBuildRequest
object
1 property
SourcePickerOptions
object
1 property 1 required
SendMessageRequest
object
2 properties 1 required
InputRecord
object
3 properties 2 required
ErrorDetail
object
The reason a request was refused. type is the family a client switches on; code is the specific reason within it; param names the offending request field when…
5 properties 3 required
InitialQueryOptions
object
2 properties 1 required
Sample
object
6 properties 6 required
Gate
object
8 properties 4 required
ErrorResponse
object
The one error envelope every refusal on this API uses.
1 property 1 required
ChoiceOptions
object
1 property 1 required
Progress
object
3 properties
QuestionnaireOptions
object
1 property 1 required
SchemaReviewOptions
object
3 properties 1 required
BuildCreated
object
2 properties 2 required
UpdateBuildRequest
object
1 property 1 required
PublishReviewAnswer
object
4 properties 1 required
Report
object
9 properties 2 required
GateAnswer
One gate resolution. EXACTLY ONE member may be set, and which member is set picks the answer kind — there is no kind property, deliberately: a discriminator th…
Build
object
A build, as the customer sees it. Some fields the core holds are deliberately not projected — a feeds-repo pull request URL and the brain's tool arguments — be…
16 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

usestring-ai-builds-api-openapi.yml Raw ↑

Other APIs String publishes across the network.

usestring-ai Browser API
usestring-ai Contexts API
usestring-ai Documentation API
usestring-ai Feeds API
usestring-ai Fetch API
usestring-ai Search API
usestring-ai Sessions API
usestring-ai Sitemap API
Where this information came from

This is an independent, third-party profile of usestring-ai Builds 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.