Access Reply Thread through one SkillBoss endpoint with unified auth, pay-as-you-go billing, and agent-ready request examples.
Endpoint: POST https://api.skillboss.co/v1/run · Model: agentmail/reply-thread
Use cURL when you want the clearest raw HTTP example. This is the fastest way to validate auth, inputs, output shape, and the canonical endpoint before wiring the API into code or agent workflows.
curl -X POST https://api.skillboss.co/v1/run \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "agentmail/reply-thread",
"inputs": {
// Your parameters here
}
}'Call Reply Thread through one stable API surface
Ship integrations faster without vendor account setup
Use the capability directly inside human and agent workflows
Reply Thread is a email api available through SkillBoss. Teams use it to add Reply Thread to apps, automations, and AI agent workflows without managing separate vendor credentials. This page gives both humans and agents one stable place to understand the capability, pricing path, and invocation pattern before they ship it into production.
Send a POST request to https://api.skillboss.co/v1/run with "model": "agentmail/reply-thread" and an "inputs" object. SkillBoss handles auth, billing, and the unified API layer. If you are testing the endpoint manually, start with the cURL or Python tab below. If you are wiring an autonomous agent, use the x402 or MPP tabs when the payment path matters.
SkillBoss gives you one API key, pay-as-you-go billing, and a consistent integration flow across many APIs. That reduces setup time and makes the endpoint easier to use in Claude Code, Cursor, Windsurf, and other agents. It also gives you a canonical public page, consistent docs, and one billing surface instead of forcing each team to juggle provider-specific auth and pricing rules.
Yes. This page is designed as a discovery surface for both humans and agents: clear capability framing, direct code examples, and a stable canonical URL make it easier to find, evaluate, and invoke. The structure is deliberate so search engines, agent runtimes, and developers can all understand what the endpoint does, how it is paid for, and which next pages matter.
Reply Thread is compatible with x402 and MPP when billed with deterministic pricing such as per-request or other fixed-cost execution. Agents can pay per call and avoid pre-funding.
One API key. 100+ models.
Call agentmail/reply-thread through SkillBoss — same endpoint, zero markup.