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

Scott Ai artifacts API

The artifacts API from Scott Ai — 1 operation(s) for artifacts.

Scott Ai artifacts API is one of 30 APIs that Scott Ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Artifacts. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against the base URL https://api.tryscott.ai.

1 operations 1 paths 5 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.tryscott.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Scott Ai artifacts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

artifacts 1
POST
/workspaces/{workspace_id}/document-artifacts
Create Document Artifact
create_document_artifact_workspaces__workspace_id__document_artifacts_post 2 params body → 200422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are CreateDocumentArtifactRequest (6 properties), CreateDocumentArtifactResponse (5 properties), ValidationError (5 properties), ChangeEntry (4 properties). Each schema is shown below with its type and property counts.

ChangeEntry
object
One semantic change emitted by the agent's writedocument tool. Field-name casing matches the agent's serialization (camelCase) so Pydantic round-trips without…
4 properties 3 required
CreateDocumentArtifactRequest
object
Body for POST /document-artifacts. Sent by the agent service when writedocument produces a new document artifact. The client UUID becomes the artifact's docume…
6 properties 4 required
ValidationError
object
5 properties 3 required
HTTPValidationError
object
1 property
CreateDocumentArtifactResponse
object
Same shape as the document-only fields of ArtifactSummary, declared here to keep the write endpoint self-contained.
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scott-ai-artifacts-api-openapi.yml Raw ↑

Other APIs Scott Ai publishes across the network.

Scott Ai access API
Scott Ai agent-counsel API
Scott Ai agent-counsel-internal API
Scott Ai agent-loop API
Scott Ai agent-loop-internal API
Scott Ai auth API
Scott Ai billing API
Scott Ai cli-version API
Scott Ai connected-sources API
Scott Ai conversations API
Scott Ai documents API
Scott Ai e2b API
Where this information came from

This is an independent, third-party profile of Scott Ai artifacts 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.