---
title: "Is the request I am about to send safe?"
method: POST
path: "/api/integration/lint"
tags: ["discovery"]
---

# Is the request I am about to send safe?

`POST /api/integration/lint`

## Request

- Base URL: `https://api.anygas.xyz/svc`
- URL: `https://api.anygas.xyz/svc/api/integration/lint`
- Auth: none declared

Every provider documents the safe way to integrate and then has no idea whether anyone followed it. Integrators discover they skipped something when it costs them. Post the request you INTEND to send and get the missing/unsafe fields with the concrete consequence of each. Severity is honest: `unsafe` means you can lose money or report a falsehood; `suboptimal` means it will cost you. IT LINTS THE REQUEST ONLY. It cannot see whether you branch on all three verification verdicts, treat `undetermined` as success, or use `serviceableNow` rather than `policyEligible` — a clean lint is NOT a correct integration, and an endpoint with no rules returns "unchecked", never "clean".

## Request body

- object

## Response `200`

findings with severity, field, consequence and fix

- object

## Other responses

- `400`: endpoint required

---

[API](https://skmtc.dev/anygas/apis/robyn-anygas-api.md) · [All operations](https://skmtc.dev/anygas/apis/robyn-anygas-api/llms.txt) · [OpenAPI document](https://skmtc.dev/anygas/apis/robyn-anygas-api/revisions/9b7498be8304?raw)