# OSS License Conflict Snapshot

> OSS License Conflict Snapshot is a paid API for AI agents from api.the402.ai, paid per call via x402, $0.084/call, status unknown (last checked 2026-09-15).

Analyzes open-source software licenses in a project to detect conflicts, incompatibilities, and compliance risks

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_29a0de8d60df4c8a/purchase
- Price: $0.084/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-the402-ai-553ea9f3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sM1sen75Uhu71E48SaPbq

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 api-the402-ai-553ea9f3 -d '<json body>'
```

Example prompt: Can you run an OSS license conflict snapshot on my project at github.com/myorg/myrepo and tell me if there are any incompatible licenses or copyleft conflicts I need to worry about before shipping?

## When to prefer this

Use this endpoint when you need a point-in-time compliance audit of open source licenses in a software project, especially before a release, acquisition due diligence, or when adding new dependencies. Prefer this over manual license review when dealing with complex transitive dependency trees or when you need a structured, machine-readable conflict report.

## Known failure modes

- Invalid or inaccessible repository URL returns an error
- Unrecognized package manager or dependency format not supported
- Repository with no detectable license files returns empty or inconclusive result
- Network timeout if dependency tree is very large
- Payment failure via x402 protocol results in no analysis being performed

## How this service works

Purchase: OSS License Conflict Snapshot

## Output

Returns a structured snapshot of license conflicts found in the scanned project, including which packages have incompatible licenses, the nature of the conflict (e.g. GPL vs MIT, AGPL copyleft), severity or risk level, and a summary of compliance issues to address.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "id"
 ],
 "properties": {
  "id": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-the402-ai-553ea9f3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.the402.ai](https://www.zero.xyz/host/api.the402.ai/llms.txt)