backend-api-demos

Access think-tars demo API endpoints for assistants, conversations, messages, and PDF uploads.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/freddomingues/think-tars --skill backend-api-demos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-api-demos
Source: https://github.com/freddomingues/think-tars/tree/main/.cursor/skills/backend-api-demos
Command: npx skills add https://github.com/freddomingues/think-tars --skill backend-api-demos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The think-tars demo API is a core integration surface for mock clients and internal demos. This skill provides a centralized reference to available endpoints, their usage patterns, and expected responses to accelerate integration work with the demos backend.

Core Features & Use Cases

  • List assistants (GET /assistants) to discover registered agents and their IDs.
  • Create conversations (POST /conversations) to start new discussions tied to a specific agent or vector store.
  • Send messages (POST /conversations/<conversation_id>/messages) to drive a dialogue flow and test tool integrations.
  • Upload PDFs (POST /upload-pdf) to seed a vector store and initialize a conversation around document content.
  • Use Case: rapidly validate contract review workflows by querying assistants, spawning conversations, and uploading contract PDFs for indexing.

Quick Start

Use the think-tars API demos skill to list assistants, create a new conversation, and upload a PDF to seed the vector store.

Frequently Asked Questions about backend-api-demos

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Flask API to expose demo endpoints for conversations and PDF uploads?

To expose demo API endpoints for conversations and PDF uploads, use this skill to reference RESTful routes under /api/demos. It defines response structures and error handling guidance for listing assistants, creating conversations, sending messages, and uploading PDFs to vector stores.

How do I upload a PDF to initialize a vector store for a conversation?

Upload a PDF to initialize a vector store by sending a POST request to the /upload-pdf endpoint. This action seeds the vector store with document content, enabling you to start a new conversation tied to that specific indexed data.

What is the process to list assistants and create a new conversation via API?

List registered agents and retrieve their IDs using the GET /assistants endpoint. Then create a new conversation by sending a POST request to /conversations, specifying the target assistant or vector store to initiate the dialogue flow.

Can I use this API to automate contract review workflows and FAQ pipelines?

Yes, you can automate contract review workflows and FAQ pipelines by listing assistants, spawning conversations, and uploading contract PDFs for indexing. The API endpoints support driving dialogue flows and testing tool integrations for these demo workflows.

How do I send messages to a conversation to test tool integrations?

Send messages to drive dialogue flow and test tool integrations by making a POST request to /conversations/<conversation_id>/messages. This endpoint allows you to interact with the conversation thread after it has been successfully created.

What are the common error statuses and handling guidance for these demo API endpoints?

The demo API endpoints provide robust error handling guidance for common HTTP statuses. This ensures clear response structures are returned when issues occur during assistant listing, conversation creation, message sending, or PDF uploading operations.