# ScriptMasterLabs SDVOSB Set-Aside Feed

> ScriptMasterLabs SDVOSB Set-Aside Feed is a paid API for AI agents from acp-x402-scriptmasterlabs.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-13).

Returns a feed of Service-Disabled Veteran-Owned Small Business (SDVOSB) set-aside federal contracting opportunities, paid per-call via USDC on Base.

## Facts

- Endpoint: GET https://acp-x402-scriptmasterlabs.onrender.com/x402/sdvosb-setaside-feed?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scriptmasterlabs-sdvosb-set-aside-feed-503e3fe9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_necc2N0mLiyVP3rkPzPVi

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 scriptmasterlabs-sdvosb-set-aside-feed-503e3fe9
```

Example prompt: Can you pull the latest SDVOSB set-aside federal contracting opportunities feed for me — I need to see what solicitations are currently reserved for service-disabled veteran-owned small businesses?

## When to prefer this

Choose this endpoint when you specifically need a feed of SDVOSB (Service-Disabled Veteran-Owned Small Business) set-aside federal contracting opportunities and are willing to pay $0.001 USDC per call via the x402 micropayment protocol on Base. Prefer this over general federal procurement APIs when your use case is SDVOSB-specific compliance or business development.

## Known failure modes

- Payment not settled in USDC on Base — 402 Payment Required returned
- Invalid or malformed properties filter string — may return empty or error response
- Downstream federal data source unavailable — empty feed or service error
- Render.com cold start latency causing timeout on first call
- Schema sparsity means unexpected or undocumented fields in response

## How this service works

Pay-per-call crypto, RWA, federal, SEC, and compliance APIs. Settled in USDC on Base via x402. Hyphen routes only (e.g. /x402/rwa-aggregates, /x402/gas-tracker).

## Output

A feed of active SDVOSB set-aside federal contracting opportunities, including solicitation details and procurement metadata relevant to service-disabled veteran-owned small businesses. The response is a JSON object (schema is minimal/example-only, so exact fields may vary at runtime).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/scriptmasterlabs-sdvosb-set-aside-feed-503e3fe9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from acp-x402-scriptmasterlabs.onrender.com](https://www.zero.xyz/host/acp-x402-scriptmasterlabs.onrender.com/llms.txt)