Social data

client.socialData wraps the three social data routes. Types: SocialDataTool, SocialDataToolDetail, SocialDataRun, SocialDataRunRequest, SocialDataToolSearch. It is client.data’s social domain.

import { createClient } from "@usenaive-sdk/vetta";
const client = createClient({ apiKey: process.env.VETTA_API_KEY! });

// 1. Find a tool (free)
const { data: tools } = await client.socialData.searchTools({ query: "tiktok video comments", platform: "tiktok", limit: 5 });
for (const tool of tools) console.log(tool.name, tool.price.text, tool.id);

// 2. Read what it takes (free)
const tool = await client.socialData.getTool(tools[0].id);
console.log(tool.input.query, tool.input.body, tool.notes);

// 3. Run it (priced)
const run = await client.socialData.run({ tool_id: tool.id, query: { url: "https://www.tiktok.com/@nasa/video/1" } });
if (run.status === "failed") throw new Error(run.error!);
console.log(run.data, `cost $${run.cost_micro_usd / 1e6}`);

Method	Route	Notes
`searchTools({ query, platform?, limit? })`	`GET /v1/social_data/tools`	Free. `{ data: SocialDataTool[] }`, best match first.
`getTool(id)`	`GET /v1/social_data/tools/{id}`	Free. Adds `input` (JSON Schema per `path` / `query` / `body`) and `notes`.
`run({ tool_id, query?, path?, body? })`	`POST /v1/social_data/runs`	Priced. Resolves when the run ends (≤ ~2 min). Each call sends a fresh `Idempotency-Key` (or your client’s `idempotencyKey()`), so calling `run()` again is a second, billed run.

A failed run resolves (it does not throw) with status: "failed" and error; refusals before a run — insufficient_credits, not_found, validation_failed — throw an ApiError.

TypeScript

Control plane

Resources

Identity & access

Automation

Account