Hi @Hainrixz, thanks for building this kit — it's exactly what we needed for our civic data platform.
Context
We're a humanitarian coordination platform for the Venezuela earthquake response (https://vnzla-ayuda.vercel.app/). We've followed the full kit workflow:
Question
endpoint submit says "Abre la plataforma -> 'Registrar una fuente'" but doesn't give the URL. The guide at tododeia.com/community/endpoint-agent-kit also doesn't link to it.
Where is the web form to submit a source proposal?
Secondary question
Our endpoints live on Supabase PostgREST, which requires three headers: apikey, Authorization: Bearer <KEY>, and Accept-Profile: public (our Supabase project has graphql_public as the default schema). The kit's propuesta schema only has a single auth_header field. Is there a standard way to declare extra headers, or should we add them to integration_notes?
Thanks!
Hi @Hainrixz, thanks for building this kit — it's exactly what we needed for our civic data platform.
Context
We're a humanitarian coordination platform for the Venezuela earthquake response (https://vnzla-ayuda.vercel.app/). We've followed the full kit workflow:
propuesta.jsonfiles withendpoint sample.endpoint validate --strict✓ on all four.endpoint audit✓ 48/48 checks.Question
endpoint submitsays "Abre la plataforma -> 'Registrar una fuente'" but doesn't give the URL. The guide attododeia.com/community/endpoint-agent-kitalso doesn't link to it.Where is the web form to submit a source proposal?
Secondary question
Our endpoints live on Supabase PostgREST, which requires three headers:
apikey,Authorization: Bearer <KEY>, andAccept-Profile: public(our Supabase project hasgraphql_publicas the default schema). The kit's propuesta schema only has a singleauth_headerfield. Is there a standard way to declare extra headers, or should we add them tointegration_notes?Thanks!