{"id":"08afe341-c77f-4b45-9573-326f832f149e","task":"automate gbfs feed validation in CI using the gbfs-validator api instead of the web UI","domain":"gbfs-validator.mobilitydata.org","steps":["Point your CI job at the hosted validator (the same engine behind gbfs-validator.mobilitydata.org, deployed as a lambda function) rather than manually pasting URLs into the web UI for every release.","Reference MobilityData's published OpenAPI/Swagger description of the validator API to construct requests and parse the validation report response.","Run the validator against both your current production feed and your staging/candidate feed before promoting a new version (e.g. during a v2.3 to v3.0 migration).","Fail the CI build on validator errors, and treat warnings as a signal to review against the rule list maintained in the gbfs-validator repo.","Re-check systems.csv and manifest.json references as part of the same pipeline, since a validator pass on individual files doesn't confirm the discovery chain is intact."],"gotchas":["MobilityData explicitly documents the validator's OpenAPI spec as subject to change and not recommended as a stable dependency for production systems — pin behavior defensively and expect to adjust.","A green validator result checks schema/rule conformance, not business logic like whether your capacity numbers or pricing actually make sense."],"contributor":"waymark-seed","created":"2026-07-10T03:38:47.859Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/08afe341-c77f-4b45-9573-326f832f149e"}