Search developer.apple.com the way its search page does (Apple's search API). Returns links, not content: each result's title, framework, type and Apple's one-line summary, grouped by section. type "all" (the default) covers documentation, the Human Interface Guidelines, sample code and App Store Connect Help, plus a WWDC Sessions section of up to 5 sessions, each with the get_wwdc_video call that reads it; "documentation", "design", "sample" or "help" (App Store Connect Help) searches only that. Read a result with get_apple_doc_content. Searches go out one at a time, 15 s apart, as Apple answers quicker ones with no results; "all" sends two.

One page of Apple's documentation as Markdown, rendered from the page's JSON, the data developer.apple.com builds the page from, in its Swift version: the symbol's kind, Apple's summary, a deprecated API's message, its declaration, the overview with its code listings, tables, term lists, notes, images and videos (with Apple's alt text), the articles it's mentioned in, a property list key's details and attributes, the Topics groups with each group's description and each member's declaration and summary, a protocol requirement's default implementations, the Relationships (conforms to, inherits from, inherited by, conforming types), platform availability and the See Also links; a sample page's Download; a tutorial overview's volumes and chapters, each tutorial with its summary, and its resources, and a tutorial's steps with the code file after each and its project files; a web-service page's (App Store Connect API, App Store Server API and the like) URL, parameters, body, response codes, properties and possible values. An App Store Connect Help page comes as its article converted to Markdown. Links in the text come as links. The include… flags append related APIs, referenced types, similar APIs and a platform analysis, read from the page's JSON.

Apple's technology index: every framework and technology with its link, its languages (swift, occ, data) and its categories, alphabetical within each category. category keeps the categories whose name contains it, or else the technologies with a tag that contains it ("Machine learning": Core ML, Create ML, Vision…), in any case; a beta technology is marked (Beta). The last segment of a technology's link ("swiftui", "storekit") is the framework search_framework_symbols takes.

The symbols in one framework's navigator index: each one's name, link and kind, without summaries. framework is the last segment of the framework's documentation link ("swiftui", "storekit"); symbolType keeps one kind; namePattern is a wildcard such as "View" or "UI", in any case; nested symbols count toward limit. Read a symbol with get_apple_doc_content.

Every page of Apple's documentation and the Human Interface Guidelines whose title contains query, in any case and as typed (no pattern syntax), from the docs map on disk (api-map/apple-docs-map.tsv, built by scripts/build-docs-map.ts; no network): each one's title, kind, technology and link, shortest titles first; technology keeps one or more frameworks. Read a page with get_apple_doc_content.

The APIs one documentation page relates to, read from that page's JSON alone: what it inherits from and conforms to, its See Also group and the first 3 APIs of each Topics group, each with its link and Apple's one-line summary.

The pages one documentation page references, read from that page's JSON alone (no further requests): each one's title, kind, Apple's summary and, for a symbol, its declaration, grouped by kind. Takes the first maxReferences in the JSON's own order, not by relevance, and leaves out the page's images and other media; filterByType keeps one role or kind.

Where one API is available, from its page's JSON: each platform with the version that introduced it and the version that deprecated it, with Apple's note, and the minimum versions; an API deprecated on every platform it supports is flagged as such. compareMode "framework" runs the same check with related APIs included.

Alternatives to one API, read from its page's JSON: for a deprecated API, first the pages its deprecation note names (Apple's replacements, scored 10/10), then its See Also group (8/10) and, with searchDepth "medium" or "deep", its Topics groups (6/10); "deep" also reads the See Also of the first results. The scores come from where an API was found, not from comparing APIs.

Links from Apple's Updates page, each with Apple's one-line summary: the release notes of each OS, Xcode and Safari; each framework's updates page ("SwiftUI updates"); and the What's new page of each past WWDC. Returns the links, not the changes; read one with get_apple_doc_content. For WWDC sessions use the WWDC tools.

Apple's Technology Overviews guides: its collections, each with Apple's summary, and the articles in each, as one tree in Apple's order. category gives one collection with everything in it; searchQuery gives a flat list of the entries that mention it, each with the collection it is in. Returns links, not the articles; read one with get_apple_doc_content.

Apple's sample-code library: project titles with links and Apple's one-line summaries, grouped by framework; read a project's page, with its Download link, with get_apple_doc_content. framework matches the project's framework in any spelling ("storekit", "Store Kit"); searchQuery matches titles first, then frameworks, paths and summaries.

WWDC sessions from the data bundled with this server (no network): each one's title, its link on developer.apple.com, whether it has a transcript and code, and its topics. year is one year or "all" (list_wwdc_years lists them); topic is a topic ID from browse_wwdc_topics or a word in the title; hasCode keeps the sessions with, or without, code.

Full-text search of the bundled WWDC transcripts and code (no network). For each session that matches, most matches first: its title, link and year, and up to 3 matches, each a transcript paragraph or the code lines around the match, with the code example's title and the time it appears. searchIn picks transcripts, code or both; language filters the code.

One WWDC session from the bundled data, as text (no network): title, year and topics; its links, including the HD and SD .mp4 downloads and the documentation it covers; the full transcript as plain text, without timestamps; every code example with the time it appears; and related sessions. Transcripts run to tens of KB: includeTranscript false leaves it out.

Code examples from the bundled WWDC sessions (no network): each with its title, its session's title, link and year, the time it appears, and the code. framework keeps the examples whose code mentions it, so "SwiftUI" matches any code that imports SwiftUI; topic, language and year filter too.

The WWDC topics in the bundled data (no network), each with its ID, link and session count. With topicId, that topic's sessions instead, filtered by year and capped by limit.

Sessions related to one WWDC session, from the bundled data (no network): first those Apple lists as related on the session's page, then sessions sharing its topics and, with includeYearRelated, sessions of the same year; each with its year, link, topics and whether it has a transcript and code.

The WWDC years in the bundled data, each with its session count, plus the total and how many sessions have code and transcripts.