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

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

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

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

12 operations 9 paths 13 schemas 4 GET2 PATCH6 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 conversations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 12

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

conversations 12
POST
/conversations/
Create Conversation
create_conversation_conversations__post body → 200422
GET
/conversations/
List Conversations
list_conversations_conversations__get 1 param → 200422
POST
/conversations/{conversation_id}/resume
Resume Conversation
resume_conversation_conversations__conversation_id__resume_post 1 param → 200422
POST
/conversations/{conversation_id}/resume/prepare
Resume Prepare
resume_prepare_conversations__conversation_id__resume_prepare_post 1 param → 200422
POST
/conversations/{conversation_id}/resume/confirm
Resume Confirm
resume_confirm_conversations__conversation_id__resume_confirm_post 1 param → 200422
POST
/conversations/{conversation_id}/resume/reject
Resume Reject
resume_reject_conversations__conversation_id__resume_reject_post 1 param → 200422
GET
/conversations/active-session
Get Active Session
get_active_session_conversations_active_session_get → 200
GET
/conversations/{conversation_id}
Get Conversation
get_conversation_conversations__conversation_id__get 1 param → 200422
PATCH
/conversations/{conversation_id}
Update Conversation
update_conversation_conversations__conversation_id__patch 1 param body → 200422
GET
/conversations/{conversation_id}/messages
Get Conversation Messages
get_conversation_messages_conversations__conversation_id__messages_get 3 params → 200422
POST
/conversations/{conversation_id}/messages
Append Messages
append_messages_conversations__conversation_id__messages_post 1 param body → 200422
PATCH
/conversations/{conversation_id}/messages/{message_id}
Update Message
update_message_conversations__conversation_id__messages__message_id__patch 2 params body → 200422

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ConversationResponse (10 properties), ConversationListResponse (8 properties), ValidationError (5 properties), ConversationCreate (4 properties). Each schema is shown below with its type and property counts.

ActiveSessionResponse
object
Response from active-session — tells browser if there's a live session to reconnect to
3 properties 1 required
ResumeConfirmationResponse
object
Response from resume/confirm — sandbox is now the active one
2 properties 2 required
ConversationCreateResponse
object
Response when creating a new conversation
2 properties 1 required
ConversationUpdate
object
For updating conversation metadata
1 property
MessageUpdate
object
For updating a specific message in a conversation
2 properties
ConversationResponse
object
Metadata only - no messages
10 properties 8 required
ResumePreparationResponse
object
Response from resume/prepare — sandbox is awake and ready for session validation
2 properties 2 required
ValidationError
object
5 properties 3 required
ResumeRejectionResponse
object
Response from resume/reject — pending sandbox cleared
2 properties 2 required
MessageAppend
object
For appending messages to a conversation
1 property 1 required
ConversationCreate
object
4 properties 1 required
HTTPValidationError
object
1 property
ConversationListResponse
object
Lightweight response for listing conversations
8 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

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