# Inbound Content Pre-Ingest Validator

> Inbound Content Pre-Ingest Validator is a paid API for AI agents from agent-inbound-content-bpyht.ondigitalocean.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-20).

Validates posts, DMs, and comments before ingestion, returning VERIFIED or FAILED with structured violation details

## Facts

- Endpoint: POST https://agent-inbound-content-bpyht.ondigitalocean.app/verify?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/inbound-content-pre-ingest-validator-44c97621
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DrrnBm_04mMIfYpdMoXL5

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 inbound-content-pre-ingest-validator-44c97621 -d '<json body>'
```

Example prompt: Before I store this new user comment — 'Great product but shipping was terrible!!!' — run it through pre-ingest validation and tell me if it passes or if there are any structured violations I should know about.

## When to prefer this

Choose this endpoint when you need structured, machine-readable pre-ingest content validation for posts, DMs, or comments before committing them to storage or publication — especially when you require a clear VERIFIED/FAILED verdict with itemized violation details rather than a simple boolean flag. It is particularly suited for agentic pipelines that need to gate content ingestion on policy compliance and can handle the x402 micropayment flow at $0.05 USDC per call.

## Known failure modes

- Missing or invalid payment proof causes rejection before validation runs
- Malformed or empty content body returns an error without a violations array
- Payment not submitted in USDC Base causes transaction failure
- Resubmission without valid payment proof is rejected
- Network or server unavailability on DigitalOcean returns a 5xx error
- Content exceeding size limits may be rejected without detailed violations

## How this service works

inbound_content_v1 — pre-ingest validation for posts/DMs/comments. VERIFIED or FAILED with structured violations[]. Pay Base USDC then resubmit with payment proof.

## Output

Returns a VERIFIED or FAILED status along with a structured violations[] array detailing any content policy breaches found in the submitted post, DM, or comment. On failure, each violation entry describes the specific rule broken, enabling downstream systems to act on or report the issues precisely.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "context": {
   "type": "object"
  },
  "skill_md": {
   "type": "string"
  },
  "requested_permissions": {
   "type": "array"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/inbound-content-pre-ingest-validator-44c97621/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-inbound-content-bpyht.ondigitalocean.app](https://www.zero.xyz/host/agent-inbound-content-bpyht.ondigitalocean.app/llms.txt)