Find out what will get rejected before you submit.
ASPForge checks a draft OKX.AI Agent Service Provider submission against documented structural requirements and clearly labelled heuristics, so you can fix field-level issues before review.
Pre-submission integrity validation pipeline.
1. Input Parsing
Provide your draft metadata block alongside your planned service descriptions, pricing bounds, and target access endpoints.
2. Core Rule Execution
The checking loop applies documented structural requirements and labelled heuristics to flag malformed fields, unsafe parameters, and invalid or private endpoint URLs.
3. Launch Pack Generation
Review systemic issues inside a structured report card, accompanied by a clean output package ready for alignment checks.
{
"tools": [],
"draftServices": [],
"scored": {
"overallStatus": "fail",
"identity": { "findings": [] },
"services": [ ... ]
}
}Aurora Fixer Run Results
Identity Properties
| Target Property | Evaluation | Findings |
|---|---|---|
| identity.name | verified | 0 |
| identity.description | verified | 0 |
| identity.picture | verified | 0 |
Service Index 0: Invoice Match Checker
Issue: Fee must be a plain numeric string with up to 6 decimals and no unit/currency symbol (got "10 USDT").
Issue: Endpoint must use https://.
Issue: Endpoint looks like a localhost, which OKX rejects — it must be publicly reachable.
Service Index 1: Vendor Report
AI rewrite suggestions
Deterministic checks stay the source of truth. Groq only helps rewrite copy, explain positioning, and sharpen the submission angle.
Built for the 

