# DatapackVibe Artifact Builder

> DatapackVibe Artifact Builder is a paid API for AI agents from api.datapackvibe.com, paid per call via x402, $0.5/call, status unknown (last checked 2026-09-15).

Builds a requested artifact (file, document, data structure, or other output) from a JSON brief describing the desired type, method, body type, and body payload

## Facts

- Endpoint: POST https://api.datapackvibe.com/build
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/datapackvibe-artifact-builder-8898d5ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hmNi_wFxWMUm_-1UiJtlL

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability datapackvibe-artifact-builder-8898d5ed -d '<json body>'
```

Example prompt: Build me an artifact using DatapackVibe — the request type is http, method is POST, body type is json, and the body should be {"name":"report","format":"csv","rows":100} so I get a generated CSV report back.

## When to prefer this

Choose this endpoint when you need to programmatically generate or construct an artifact from a structured JSON brief and want a pay-per-use, agent-friendly API. It is well-suited for agentic workflows on the DatapackVibe platform where other sibling endpoints handle Ethereum transaction decoding, event log parsing, or EIP-712 analysis — use this endpoint specifically when the goal is artifact creation rather than blockchain data interpretation.

## Known failure modes

- Missing required 'input' field returns a validation error
- Invalid or unsupported bodyType enum value causes a 400-level error
- Malformed body object may result in a failed build with an error message
- Payment not provided or invalid x402 payment causes a 402 Payment Required response
- Ambiguous or underspecified brief may produce an unexpected or empty artifact
- Output type mismatch between requested and returned artifact format

## How this service works

Build a requested artifact from a JSON brief

## Output

The endpoint returns a constructed artifact as defined by the output specification in the request. The artifact type and structure depend on what was specified in the brief — this could be a file, document, JSON object, or other data structure matching the requested output type and example schema.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/datapackvibe-artifact-builder-8898d5ed/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.datapackvibe.com](https://www.zero.xyz/host/api.datapackvibe.com/llms.txt)