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 documents API

The documents API from Scott Ai — 9 operation(s) for documents.

Scott Ai documents 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 Documents. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 14 operations across 9 paths, and defines 16 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.

14 operations 9 paths 16 schemas 2 DELETE5 GET2 PATCH5 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 documents API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 14

Across 9 paths, the API surfaces 14 operations — 2 DELETE, 5 GET, 2 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.

documents 14
POST
/documents/
Create Document
create_document_documents__post body → 200422
GET
/documents/
List Documents
list_documents_documents__get 3 params → 200422
GET
/documents/{document_id}
Get Document
get_document_documents__document_id__get 1 param → 200422
PATCH
/documents/{document_id}
Update Document
update_document_documents__document_id__patch 1 param body → 200422
DELETE
/documents/{document_id}
Delete Document
delete_document_documents__document_id__delete 1 param → 200422
POST
/documents/{document_id}/versions
Create Document Version
create_document_version_documents__document_id__versions_post 1 param body → 200422
GET
/documents/{document_id}/coordinator-context
Get Document Coordinator Context
get_document_coordinator_context_documents__document_id__coordinator_context_get 1 param → 200422
GET
/documents/{document_id}/comments
Get Document Comments
get_document_comments_documents__document_id__comments_get 1 param → 200422
POST
/documents/{document_id}/comments
Create Comment
create_comment_documents__document_id__comments_post 1 param body → 200422
PATCH
/documents/{document_id}/comments/{comment_id}
Update Comment
update_comment_documents__document_id__comments__comment_id__patch 2 params body → 200422
DELETE
/documents/{document_id}/comments/{comment_id}
Delete Comment
delete_comment_documents__document_id__comments__comment_id__delete 2 params → 200422
POST
/documents/images
Upload Document Image
upload_document_image_documents_images_post 2 params body → 200422
GET
/documents/images/{file_id}
Resolve Document Image
resolve_document_image_documents_images__file_id__get 1 param → 200422
POST
/workspaces/{workspace_id}/document-images
Upload Agent Document Image
upload_agent_document_image_workspaces__workspace_id__document_images_post 2 params body → 200422

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are DocumentResponse (15 properties), DocumentListResponse (14 properties), DocumentCreate (11 properties), CommentThreadResponse (10 properties). Each schema is shown below with its type and property counts.

Body_upload_agent_document_image_workspaces__workspace_id__document_images_post
object
1 property 1 required
CommentUpdate
object
2 properties
DocumentListResponse
object
14 properties 9 required
ResolvedImageResponse
object
2 properties 2 required
ValidationError
object
5 properties 3 required
CommentThreadResponse
object
Top-level comment with nested replies
10 properties 9 required
DocumentUpdate
object
6 properties
DocumentImageResponse
object
2 properties 2 required
CoordinatorContextResponse
object
Context needed to resume coordinator for document revision
3 properties 3 required
Body_upload_document_image_documents_images_post
object
1 property 1 required
CommentCreate
object
4 properties 1 required
HTTPValidationError
object
1 property
DocumentCreate
object
11 properties 2 required
DocumentResponse
object
15 properties 10 required
CommentResponse
object
10 properties 10 required
DocumentVersionCreate
object
Schema for creating a new document version
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scott-ai-documents-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 artifacts 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 e2b API
Where this information came from

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