Department of Better Technology
The Department of Better Technology (DOBT), founded in 2013 by former Presidential Innovation Fellows and later acquired by CityBase, builds Screendoor — a form-building and submission- management platform used by government agencies and organizations such as ProPublica, the Los Angeles Times, the Consumer Financial Protection Bureau, and the Ford Foundation to run paperless intake, evaluation, and approval workflows. The Screendoor REST API programmatically manages sites, projects, forms and form fields, workflow statuses, labels, responses (submissions), response labels, and reviewer assignments, using API-key authentication, offset pagination with RFC 5988 Link headers, and an explicit API version.
Department of Better Technology publishes 8 API contracts indexed on the APIs.io network, including Files API, Forms API, Labels API, and 5 more. Tagged areas include Company, Forms, Government, GovTech, and Civic Technology.
The Department of Better Technology catalog on APIs.io includes 1 Spectral governance ruleset.
Department of Better Technology’s developer surface includes documentation, API reference, support, engineering blog, signup flow, authentication, and 17 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Surveys, Market Research and Experience Management | undeclared | - | - | 1 |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 8
Individual APIs this provider publishes, each with its own machine-readable definition.
Department of Better Technology Files API
Upload files referenced by response fields.
Department of Better Technology Forms API
Manage the form fields collected for a project.
Department of Better Technology Labels API
Manage labels used to tag responses within a project.
Department of Better Technology Projects API
Manage projects (forms and their workflow) within a site.
Department of Better Technology Response Assignments API
Assign users or teams to an individual response.
Department of Better Technology Response Labels API
Attach or detach labels on an individual response.
Department of Better Technology Responses API
Create, read, update, trash, and recover form submissions.
Department of Better Technology Statuses API
Manage the status workflow stages for a project's responses.
Scroll for all 8
Open Collections 8
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Screendoor Files API
OPEN COLLECTIONScreendoor Files Forms API
OPEN COLLECTIONScreendoor Files Labels API
OPEN COLLECTIONScreendoor Files Projects API
OPEN COLLECTIONScreendoor Files Response Assignments API
OPEN COLLECTIONScreendoor Files Response Labels API
OPEN COLLECTIONScreendoor Files Responses API
OPEN COLLECTIONScreendoor Files Statuses API
OPEN COLLECTIONScroll for all 8
Agent Skills 3
Packaged agent skills for driving this provider's APIs from an AI assistant.
Assign and review a submission
AGENT SKILLBuild a Screendoor form
AGENT SKILLCollect and triage submissions
AGENT SKILLSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
OpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Department of Better Technology API — frequently asked questions
Does Department of Better Technology have an API?
Yes. APIs.io lists 8 APIs from Department of Better Technology, including Department of Better Technology Files API, Department of Better Technology Forms API and Department of Better Technology Labels API, and 5 more.
Is there an OpenAPI specification for the Department of Better Technology API?
Yes. APIs.io indexes 8 OpenAPI specifications for Department of Better Technology, each linked for download from this page.
How do I authenticate with the Department of Better Technology API?
Department of Better Technology uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Department Of Better Technology Authentication.
Is the Department of Better Technology API ready for AI agents?
Department of Better Technology has a Kin Score of 31.1 out of 100 (thin) and an Agent Readiness score of 18.2 (agent-aware), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.