Voidly × ChatGPT
Your GPT.
More context.
Give a Custom GPT live censorship data via the Voidly OpenAPI Action.
Import the ActionAsk about domain accessibility, country comparisons, citable incidents and 7-day shutdown forecasts. Check the returned timestamps and evidence; a connection does not guarantee fresh data or prove intentional censorship.
01 / Connect
Import the schema.
Published setup for ChatGPT. Host menus can change; see the current host documentation if they differ.
https://voidly.ai/openapi.jsonIn GPT Builder, open Configure → Actions → Create new action.
Import the schema from https://voidly.ai/openapi.json.
No auth needed for the public read endpoints.
Your GPT can now answer “what is censored in country X” from live data.
Ask a better question.
Example prompts · answers depend on the returned data.
“Is WhatsApp blocked in Iran right now?”
“Compare internet censorship in China vs Russia.”
“Give me a citable report for the latest shutdown in Pakistan.”
“What is the 7-day shutdown risk for Ethiopia?”
“How fresh and reliable is the censorship data for this country?”
“Which ISPs censor the most in Turkey?”
Public access, freshness & source terms
The public read endpoints do not require an API key. Other routes may require credentials, and individual endpoints have their own limits. Configure the displayed MCP command in the host yourself; this page does not install or run it.
Measurements, incidents and forecasts are different kinds of output. A forecast estimates risk, and an outage is not by itself proof of intentional censorship. Inspect source timestamps, confidence and limitations before citing a result.
Voidly-original data and upstream materials can have different licenses. Read the dataset and source terms.
Published ChatGPT setup →Keep the source close