Buenos Aires Open Data Publishers (data.buenosaires.gob.ar)

buenosairesckan/list-organizations

Lists the slugs of the publishing organisations on the Buenos Aires open data portal (data.buenosaires.gob.ar), such as ministries and agencies. Use a slug to search for that publisher's datasets. Served by Eden Engine; not an official data.buenosaires.gob.ar product.

activeper callv1

Price

$0.0026 per call

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.

Data source

Buenos Aires Open Data (data.buenosaires.gob.ar)

Source: Gobierno de la Ciudad de Buenos Aires (data.buenosaires.gob.ar). Contents are licensed under Creative Commons Reconocimiento 2.5 Argentina; credit the Gobierno de la Ciudad de Buenos Aires. Served by Eden Engine; not an official Gobierno de la Ciudad de Buenos Aires product.

Use it

Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.

Connect once and your AI can find and run this tool, and any other it needs.

Install it Create an account

agent

// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "buenosairesckan/list-organizations" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "buenosairesckan/list-organizations" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "buenosairesckan/list-organizations", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "buenosairesckan/list-organizations", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

Charge	Price
Per call	$0.0026

Updated: Oct 21, 2026

Input and output schemas

Input schema

input_schema.json

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

Output schema

output_schema.json

{
  "type": "object",
  "required": [
    "results"
  ],
  "properties": {
    "results": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Organisation slugs on the portal, under `results`."
    }
  },
  "description": "Organisation slugs on the portal, under `results`.",
  "additionalProperties": true
}