Skip to content
Eden Engine
Get started

San Francisco 311 Service Types (Open311)

sf311open311/list-services

The list of request types San Francisco 311 accepts through its Open311 interface: service code, service name, request group (such as Repair or Cleaner streets) and type. Use a service_code from this list to filter the San Francisco service request search. City and County of San Francisco data, passed through unmodified and served by Eden Engine; not an official City 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

City and County of San Francisco (DataSF)

Data from the City and County of San Francisco 311 Open311 service (mobile311.sfgov.org), released under the Public Domain Dedication and License v1.0. Passed through unmodified. Served by Eden Engine; not an official City and County of San Francisco 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 itCreate an account
agent
// 1. search: find the tool
omnial_search({ query: "what you need" })

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

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

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "sf311open311/list-services", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "sf311open311/list-services", 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.

ChargePrice
Per call
$0.0026
Updated
Oct 24, 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": "object",
        "properties": {
          "type": {
            "type": "string"
          },
          "group": {
            "type": "string"
          },
          "metadata": {
            "type": "boolean"
          },
          "service_code": {
            "type": "string",
            "description": "The code to pass as service_code to the request search."
          },
          "service_name": {
            "type": "string"
          }
        },
        "additionalProperties": true
      }
    }
  },
  "description": "The service types under `results`.",
  "additionalProperties": true
}