Pickaxe API

Name: Pickaxe API
Brand: Pickaxe API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLLanguage Modelsbearer5 EndpointsREST

For Agents

Create and manage AI chatbot applications on Pickaxe Studio. Build prompt-based chatbots, upload knowledge documents, retrieve chat history, and configure bot behavior programmatically.

Install Jentic One Beta

Connect the Pickaxe API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pickaxe API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Pickaxe API.

Create new AI chatbot applications with custom prompts, instructions, and personality settings

Update existing Pickaxe chatbot configurations including prompt text and response behavior

Retrieve full conversation history from deployed chatbots for analysis and quality monitoring

GET STARTED

Start building with Pickaxe API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Pickaxe API for, with concrete tasks.

★ Custom AI Chatbot Deployment

Create and deploy AI chatbot applications with tailored prompts, personality, and knowledge bases through the Pickaxe platform. Each Pickaxe functions as a standalone conversational AI app that can be embedded on websites or shared via link. The API enables programmatic creation and updates, allowing teams to manage fleets of specialized chatbots for different use cases such as customer support, product recommendations, or internal knowledge assistants.

Create a new Pickaxe chatbot via POST /studio/pickaxe/create with a customer support prompt and friendly personality settings

Knowledge Base Management

Upload and manage documents that serve as the knowledge foundation for Pickaxe chatbots. Documents are processed and indexed so the chatbot can reference them when answering user questions. This enables building domain-specific assistants that draw from company documentation, FAQ sheets, or product manuals without requiring model fine-tuning.

Upload a product FAQ document to Pickaxe ID ABC123 via POST /studio/pickaxe/{pickaxeId}/documents to expand the bot's knowledge base

Conversation Analytics

Retrieve and analyze chat history from deployed Pickaxe chatbots for quality monitoring, user intent analysis, and response improvement. The history endpoint returns full conversation threads including user messages and bot responses, enabling teams to identify common questions, detect response quality issues, and gather training data for prompt refinement.

Retrieve the full chat history via GET /studio/pickaxe/history, analyze the last 50 conversations for common user questions, and identify topics where the bot gave unsatisfactory responses

AI Agent Bot Fleet Management via Jentic

AI agents managing multiple chatbot deployments can create, update, and monitor Pickaxe bots through Jentic without managing bearer tokens directly. The agent searches for chatbot management operations, loads endpoint schemas, and executes bot creation or document uploads with Jentic handling authentication for the Pickaxe Studio platform.

Search Jentic for 'create an AI chatbot', load the Pickaxe create operation, and deploy a new support bot with instructions tailored to a specific product line

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for pickaxe api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/studio/pickaxe/create

Create a new AI chatbot application

PUT

/studio/pickaxe/{pickaxeId}

Update an existing Pickaxe chatbot configuration

GET

/studio/pickaxe/{pickaxeId}

Retrieve Pickaxe chatbot details and settings

GET

/studio/pickaxe/history

Retrieve conversation history across chatbots

POST

/studio/pickaxe/{pickaxeId}/documents

Upload knowledge documents to a Pickaxe

POST

/studio/pickaxe/create

Create a new AI chatbot application

PUT

/studio/pickaxe/{pickaxeId}

Update an existing Pickaxe chatbot configuration

GET

/studio/pickaxe/{pickaxeId}

Retrieve Pickaxe chatbot details and settings

GET

/studio/pickaxe/history

Retrieve conversation history across chatbots

POST

/studio/pickaxe/{pickaxeId}/documents

Upload knowledge documents to a Pickaxe

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Pickaxe Bearer tokens are stored encrypted in the Jentic MAXsystem vault. Agents receive authenticated requests with proper Authorization headers — raw tokens never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create an AI chatbot' or 'upload knowledge documents to a bot') and Jentic returns matching Pickaxe operations with input schemas including prompt configuration fields and document upload parameters.

Time to first call

Direct Pickaxe integration: under 1 day for token setup and endpoint understanding. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Pickaxe API through Jentic.

Why is there no official OpenAPI spec for Pickaxe API?

Pickaxe does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pickaxe API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Pickaxe API use?

Pickaxe uses Bearer token authentication. The token is included in the Authorization header for all API requests. Through Jentic, Bearer tokens are stored in the MAXsystem vault and injected into requests automatically.

Can I create a chatbot with a custom knowledge base?

Yes. First create the Pickaxe chatbot via POST /studio/pickaxe/create with your prompt instructions, then upload documents to it using POST /studio/pickaxe/{pickaxeId}/documents. The chatbot will reference these documents when answering user questions, providing responses grounded in your specific content.

How do I retrieve conversation logs from a deployed chatbot?

Use GET /studio/pickaxe/history to retrieve conversation logs across your chatbots. The endpoint returns full conversation threads including user messages and bot responses, which you can filter and analyze for quality monitoring or prompt improvement.

How do I deploy a new chatbot through Jentic?

Search Jentic for 'create an AI chatbot application' to find the POST /studio/pickaxe/create operation. Load the schema to see configuration options (prompt, personality, response settings), then execute with your desired chatbot parameters. Jentic handles bearer token authentication for the Pickaxe platform.

Pickaxe API

Connect the Pickaxe API to your agent

Capabilities

Start building with Pickaxe API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs