Add underscoredone submit

[oritzv]

Added cors header checker api

[greptile-apps]

Greptile Summary

This PR adds a new underscoredone provider — a CORS Header Checker utility API — consisting of a PAY.md metadata file and an openapi.json spec. The service accepts a URL and optional origin, makes a real HTTP request with an Origin header, and returns the six standard Access-Control-* response headers along with derived cors_enabled and origin_allowed flags, billed at $0.01 USDC per call via the x402 protocol on Base or Solana.

• The PAY.md frontmatter is complete and well-formed: all required fields (name, title, description, use_case, category, service_url, openapi.path) are present, and the Spend-aware usage section gives clear cost-reduction guidance.
• The openapi.json is a valid OpenAPI 3.1.0 spec with thorough x-ai-instructions, x-guidance, and x402 payment metadata; a minor schema inconsistency exists where status and error are always present in responses (per the guidance) but are absent from CheckResponse.required.

Confidence Score: 4/5

Safe to merge; both files are additive-only and isolated to the new provider directory.

The submission is clean and well-structured. The only notable issue is that status and error are omitted from CheckResponse.required despite the guidance describing them as always-present fields — this mismatch could cause agent consumers to mishandle those fields. It is not blocking, but worth resolving before the spec is widely adopted.

openapi.json — specifically the CheckResponse required array.

Important Files Changed

Filename	Overview
providers/underscoredone/cors-header-checker/PAY.md	Well-formed provider metadata with all required frontmatter fields, correct service_url, appropriate category, and a concise Spend-aware usage section.
providers/underscoredone/cors-header-checker/openapi.json	Valid OpenAPI 3.1.0 spec with x402 payment metadata and clear AI guidance; the CheckResponse schema omits status and error from required even though the guidance implies both are always present (just nullable).

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant Client
    participant CORSCheckerAPI as CORS Checker API
    participant x402 as x402 / USDC Payment
    participant TargetURL as Target URL

    Client->>CORSCheckerAPI: "POST /check {url, origin}"
    CORSCheckerAPI-->>Client: 402 Payment Required (if no valid payment)
    Client->>x402: Pay $0.01 USDC (Base or Solana)
    x402-->>CORSCheckerAPI: Payment confirmed
    CORSCheckerAPI->>TargetURL: HTTP request with Origin header
    TargetURL-->>CORSCheckerAPI: Response + CORS headers
    CORSCheckerAPI-->>Client: "CheckResponse {cors_enabled, origin_allowed, headers, status, error}"

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant Client
    participant CORSCheckerAPI as CORS Checker API
    participant x402 as x402 / USDC Payment
    participant TargetURL as Target URL

    Client->>CORSCheckerAPI: "POST /check {url, origin}"
    CORSCheckerAPI-->>Client: 402 Payment Required (if no valid payment)
    Client->>x402: Pay $0.01 USDC (Base or Solana)
    x402-->>CORSCheckerAPI: Payment confirmed
    CORSCheckerAPI->>TargetURL: HTTP request with Origin header
    TargetURL-->>CORSCheckerAPI: Response + CORS headers
    CORSCheckerAPI-->>Client: "CheckResponse {cors_enabled, origin_allowed, headers, status, error}"

Loading

_{Reviews (1): Last reviewed commit: "Add underscoredone APIs to pay-skills re..." | Re-trigger Greptile}

[greptile-apps]

status and error missing from CheckResponse.required

The x-ai-instructions state that every response always includes status (null when the target is unreachable) and error (null on success), yet neither field appears in the required array of CheckResponse. Agents that read the schema strictly will treat both as optional/absent, so they may skip null-handling and crash when the fields do appear. Both are nullable but always present and should be listed in required alongside their anyOf nullable types.