Trust score
How is this computed?Composite of 5 axes from our methodology (proof-based officialness, live verification, metadata completeness, license clarity, agent readiness).
- Officialnessweight 25%40/100
40/100 from 5 proof signals (domain / portal-backlink / GitHub-org / reciprocal / policy).
- Availabilityweight 25%40/100
Verification has failed 1 consecutive time.
- Metadata completenessweight 20%60/100
6 of 10 recommended metadata fields populated.
- License clarityweight 15%50/100
License info not yet tracked for APIs (datasets only).
- Agent readinessweight 15%35/100
Docs URL present · Homepage URL present · Topic tags assigned
Official Proof
Public Sector APIProof Evidence
official domain (data.gouv.fr) (catalog: api_gouv_fr)
Data schema (2 fields)
| Field | Type | Description |
|---|---|---|
| header | object | — |
| entity | array | — |
Schema inferred from the distribution file's first records 2 days ago. Column types are sampled estimates, not source-declared.
Query the data
Pick columns and a sort, then fetch a live preview straight from the source.
Sample data (1 record)
Record 1entity: [] · header: {"timestamp":1783133512,"incrementality"
{
"entity": [],
"header": {
"timestamp": 1783133512,
"incrementality": "FULL_DATASET",
"gtfs_realtime_version": "2.0"
}
}Live sample captured at profiling time — values may have changed upstream.
Verification Status
Using the API
Configuration
- Base URL
- https://h34.hanoverdisplays.com/beziers/gtfsrt/api-1.0/gtfs-rt/trip-updates.json
Query examples
curl -sL 'https://h34.hanoverdisplays.com/beziers/gtfsrt/api-1.0/gtfs-rt/trip-updates.json' -o data.jsonFull ndjson file download — the schema shown was inferred from the file's first records.
Machine-readable & source
Embed this badge in a README or wiki — it always shows the latest verification state and quality tier.