Hi Vercel team,

We need to audit an existing natural Cron Job run on Hobby without triggering any test invocation or changing the application.

Runtime Logs documentation lists requestType:cron, but describes requestType as a framework/rendering type.

1. Does this provider-generated value distinguish a scheduler-triggered invocation from the dashboard Run button or a direct HTTP request to the same route?
2. Which supported API, CLI export, or provider-issued execution receipt includes the native origin classification together with requestId, deploymentId, path and UTC timestamp on Hobby?
3. If this origin evidence is not exposed, can Vercel confirm that limitation or identify the supported read-only source?

Selecting requestType through the observability events API returned HTTP 400 for vercel.proxy_response and vercel.log. Removing that field allowed HTTP 200 queries with empty results; we are not treating those responses as proof of origin.

Please provide the supported endpoint/schema or a sanitized response example. We are asking about the evidence source, not requesting manual job execution, a plan change or paid services.

Reference: https://vercel.com/docs/logs/runtime

No project/account identifiers, credentials, customer data, private logs or attachments are included. Thank you.