Tweets is a chat api from manual that teams use to power assistants, copilots, and agent loops through one SkillBoss endpoint.
It returns structured output from model twitterapi_io/tweets, supports per request billing, and gives agents a stable invocation contract instead of vague routing hints.
Power assistants, copilots, and agent loops
Generate text, summaries, and reasoning outputs
Route prompts through one unified API key
Direct Answer
Tweets is a chat api exposed through SkillBoss. Use it when you need to power assistants, copilots, and agent loops, want one stable request surface, and need a model ID and billing path that both humans and agents can act on quickly.
Best Fit
You want Tweets behind one stable SkillBoss endpoint instead of wiring up manual directly.
You need a canonical page with copyable request shape, pricing context, and model ID for developer handoff or agent routing.
You want deterministic per-call billing that can support machine payment flows.
Watchouts
If you need vendor-specific account features outside the SkillBoss gateway, you may still need native setup.
If you need a different capability category, use the catalog and vendor links below instead of forcing the wrong endpoint.
Capability Snapshot
Endpoint
POST /v1/run
Auth
Bearer API key
Model
twitterapi_io/tweets
Payments
Standard API key, x402, Payment Later
Canonical URL
https://www.skillboss.co/hi/use/tweets-api
Step 1
Use https://api.skillboss.co/v1/run with a standard JSON body and your SkillBoss API key.
Step 2
Set "model": "twitterapi_io/tweets" so your app or agent routes to the intended capability consistently.
Step 3
This API can support machine payments via x402 and Payment Later. Keep the standard API key flow as the default unless your agent specifically benefits from machine-native payment rails.
Request Shape
{
"model": "twitterapi_io/tweets",
"inputs": {
"messages": [
{
"role": "user",
"content": "Give me a concise overview of Tweets."
}
]
}
}Example Response
{
"id": "run_123",
"output": {
"text": "Tweets completed the request successfully."
}
}For Humans
Product teams shipping chat, summarization, and reasoning features
Internal tools that need prompt-driven workflows fast
Developers comparing models without vendor-by-vendor integration work
For Agents
Coding and workflow agents that need strong text generation
Routing layers that choose different models for different tasks
Assistants that call one stable endpoint instead of many vendor APIs
Power assistants, copilots, and agent loops
Generate text, summaries, and reasoning outputs
Route prompts through one unified API key
curl -X POST https://api.skillboss.co/v1/run \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "twitterapi_io/tweets",
"inputs": {
"messages": [
{
"role": "user",
"content": "Give me a concise overview of Tweets."
}
]
}
}'import requests
response = requests.post(
"https://api.skillboss.co/v1/run",
headers={
"Authorization": "Bearer YOUR_API_KEY",
"Content-Type": "application/json"
},
json={
"model": "twitterapi_io/tweets",
"inputs": {
"messages": [
{
"role": "user",
"content": "Give me a concise overview of Tweets."
}
]
}
}
)
print(response.json())Payment Options
This API can support machine payments via x402 and Payment Later. This endpoint has deterministic per-request pricing, which makes it a reasonable fit for pay-per-call machine payment flows such as x402 and Stripe-backed Payment Later.
x402
Status: Supported. Use x402 when an agent can know the exact price before execution and pay onchain request by request.
Payment Later
Status: Supported. Use Payment Later when an agent should pay with card-backed machine payments instead of prefunded crypto.
from x402.client import X402Client
client = X402Client(
wallet_address="0xYOUR_WALLET",
private_key="0xYOUR_PRIVATE_KEY",
network="base",
)
response = client.post(
"https://api.skillboss.co/v1/run",
json={
"model": "twitterapi_io/tweets",
"inputs": {
"messages": [
{
"role": "user",
"content": "Give me a concise overview of Tweets."
}
]
}
}
)
print(response.json())import requests
import stripe
stripe.api_key = "sk_test_your_stripe_key"
spt = stripe.PaymentMethod.create_shared_token(
payment_method="pm_your_payment_method",
amount=100,
currency="usd",
)
response = requests.post(
"https://api.skillboss.co/v1/run",
headers={
"Authorization": f"Payment {spt.id}",
"Content-Type": "application/json",
},
json={
"model": "twitterapi_io/tweets",
"inputs": {
"messages": [
{
"role": "user",
"content": "Give me a concise overview of Tweets."
}
]
}
}
)
print(response.json())Discover
Compare adjacent capabilities and find alternatives from one unified catalog.
Vendor
See the rest of this vendor's public endpoints and compare them side by side.
Agents
Use the same capability inside agent tools instead of maintaining separate provider setup.
Canonical
The canonical page, model ID, and request surface are visible above the fold, which reduces ambiguity for searchers and agents.
Extractable
Direct-answer, best-fit, watchout, and invocation sections expose the critical facts in short standalone passages.
Operational
Payment guidance is separated from quick start, so users can launch first and choose x402 or Payment Later only when it actually fits.
Tweets is a chat api available through SkillBoss. Teams use it for power assistants, copilots, and agent loops without managing separate vendor credentials.
Send a POST request to https://api.skillboss.co/v1/run with "model": "twitterapi_io/tweets" and an "inputs" object containing the capability-specific parameters shown in the request example on this page.
Successful responses return a run identifier plus a structured output payload. The exact shape varies by capability, and this page shows a representative example response block so developers and agents can plan parsing correctly.
Tweets uses per request pricing on SkillBoss. Check the pricing card and payment section on this page before wiring billing logic into your app or agent.
This API can support machine payments via x402 and Payment Later. This endpoint has deterministic per-request pricing, which makes it a reasonable fit for pay-per-call machine payment flows such as x402 and Stripe-backed Payment Later.
The underlying vendor for this endpoint is manual. SkillBoss provides the unified API surface, billing layer, and canonical discovery page for Tweets.
Get your API key, call twitterapi_io/tweets, and use this capability in both product workflows and AI agents.