USCIS Policy Manual API: Query Immigration Guidance by Volume, Part and Chapter

Short answer: the USCIS Policy Manual is the agency's own instruction set for the officers who adjudicate immigration benefits, and it is 12 volumes. USCIS says it is "to be followed by all USCIS officers." It is replacing the Adjudicator's Field Manual, and unlike 8 C.F.R. it changes by policy update rather than by notice-and-comment rulemaking. That is why it moves faster than the regulation underneath it, and why an immigration case-management product that only watches 8 C.F.R. is watching the slow layer. This post covers the structure, the unusual citation form, what weight the Policy Manual carries, and how to query it with corpusType=AGENCY_GUIDANCE and source=uscis_policy_manual.

Reviewed and corrected on 12 October 2026. This is general information, not legal advice.

TL;DR

• The addressable unit is a chapter, not a numbered section. A cite looks like "USCIS Policy Manual, Vol. 12, Pt. D, Ch. 3", so there is no single number to key a record on the way there is for 8 U.S.C. 1255.
• 12 volumes, about 460 chapters. USCIS's table of contents listed 459 chapter pages on 12 October 2026. All of it sits behind one search endpoint with corpusType=AGENCY_GUIDANCE and source=uscis_policy_manual, and the live GET /boards registry lists it with a monthly cadence.
• USCIS tells its officers to follow it, and says it creates no legally enforceable right. It states agency policy, and it is replacing the Adjudicator's Field Manual.
• It changes by policy update, not by rulemaking. A Policy Manual update can shift how a benefit is adjudicated without a single word of 8 C.F.R. changing, which is exactly why monitoring it matters.
• The three-layer stack is INA at 8 U.S.C., then 8 C.F.R., then the Policy Manual. Each layer answers a different question, and the double citation form of the INA trips most parsers.
• This source is not BIA decisions, not court case law, and not Federal Register immigration rules. Those rules live in a separate FEDERAL_REGISTER corpus of more than 196,000 sections.

This post belongs to our federal agency guidance series.

For related coverage, see Federal Agency Guidance API: 53 Sub-Regulatory Sources in One Endpoint, MPEP and TMEP API: Patent and Trademark Examining Procedure You Can Query for the same manual-shaped problem on the IP side, and DOJ Justice Manual API: 1,548 Sections of Federal Prosecution Policy.

Disclosure: we build Vaquill AI. The corpus totals here are the figures we publish for this API and were last checked on 2026-10-09. The chapter and volume counts come from USCIS's own table of contents, read on 12 October 2026. The GET /us/statutes/coverage endpoint returns the totals; it needs an API key but costs no credits.

What the Policy Manual is

USCIS adjudicates benefits. Adjustment of status, naturalization, employment authorization, waivers, humanitarian relief. Officers making those decisions need something more operational than a regulation, and the Policy Manual is that thing.

It is written by USCIS for USCIS. It states agency policy on how a benefit is adjudicated, what evidence satisfies a requirement, and how discretion gets exercised.

For years the equivalent document was the Adjudicator's Field Manual, a legacy compilation that the Policy Manual is replacing. USCIS retired the AFM in May 2020 and has been moving its content into the Policy Manual since. If your internal knowledge base still cites the AFM, check the cite against the Policy Manual and USCIS's crosswalk between the two.

Be precise about the legal weight, and use USCIS's own words. The Policy Manual landing page says the Manual "contains the official policies of USCIS" and "is to be followed by all USCIS officers in the performance of their duties but it does not remove their discretion in making adjudicatory decisions." It also says it "does not create any substantive or procedural right or benefit that is legally enforceable by any party against the United States or its agencies or officers or any other person." So it is agency policy, not a regulation and not a statute. We have not found USCIS addressing how much weight a court gives it, so cite the statute and regulation for what the law requires and the Manual for how officers are told to act.

That distinction cuts both ways in practice. You can't rest a legal argument on the Policy Manual alone. You also can't predict what the service center will do without it.

A short history: from field manual to one online manual

For a long time, USCIS officers worked from a patchwork: the Adjudicator's Field Manual plus a drawer full of memos. In January 2013 USCIS prepared to launch the Policy Manual to pull that together. A law-firm blog post reports that Director Alejandro Mayorkas said on January 15, 2013 that the Manual was meant to bring "consistency, predictability and transparency" to the authority and policies behind USCIS adjudication. The blog's own words, not a quotation of Mayorkas, describe the earlier resources as "independently housed by the issuing agency" and say they would be "replaced by a centralized repository of all relevant policy guidance and legal authority."

The Field Manual lasted a few more years. USCIS's own Volume 1, Part A page says that "In May 2020, USCIS retired its Adjudicator's Field Manual (AFM)," that remaining AFM content now sits under the matching Policy Manual part (the Policy Manual landing page says as PDFs), and that where the Manual conflicts with that leftover content or with policy memos, "the updated information in the Policy Manual prevails." So an old AFM cite may still lead to text, and the Policy Manual wins any conflict.

The structure, and why it is integration-relevant

The manual is organized as volumes, then parts, then chapters. Twelve volumes, each covering one benefit family or cross-cutting topic. The volume titles below are the ones on USCIS's Policy Manual page.

Underneath those twelve volumes, USCIS's table of contents listed 459 chapter pages in 100 parts on 12 October 2026, and the chapter is the unit that carries text. Chapter counts per volume range from 5 (Volume 4) to 74 (Volume 2), and the totals move whenever USCIS adds a chapter.

The citation form breaks ordinary parsers

Here is the shape of a real cite:

USCIS Policy Manual, Vol. 12, Pt. D, Ch. 3

USCIS's own pages use a shorter house style for the same address, such as "8 USCIS-PM K.2" for Volume 8, Part K, Chapter 2. Both forms mean the same chapter, so an extractor needs to accept both. Compare that to the two layers underneath it:

The Policy Manual has no single section number. The address is a triple, and the middle element is a letter. A regex written for \d+\s+C\.F\.R\.\s+\d+ finds nothing, and a database schema with one section_number column has nowhere to put a part letter.

There is a second trap, and it belongs to immigration specifically. The INA has two citation forms for the same provision. Practitioners cite INA 245; the codified form is 8 U.S.C. 1255. INA 212(a) is 8 U.S.C. 1182(a). INA 101(a)(15) is 8 U.S.C. 1101(a)(15).

Your extractor has to handle both, because attorneys write the INA form and the corpus is keyed on the codified form. If you normalize only one direction, half your citations dead-end, which is the general citation-parsing problem in miniature.

Look at the two inputs on the left. 8 C.F.R. changes through Federal Register rulemaking, which means a proposed rule, a comment period, and a final rule. The Policy Manual changes through a policy update, which USCIS issues on its own.

One of those paths takes months and is loudly telegraphed. The other can land on a Tuesday. If you only watch the regulation, you find out about the policy shift from a client. USCIS labels each change on its updates log as a Policy Alert or a Technical Update. When we read that log on 12 October 2026, the newest entries were a Technical Update on October 2, 2026 and two Policy Alerts dated September 23, 2026.

A quick story: a policy change with no rulemaking

If you want to see the "policy update, no rulemaking" path in action, read the update log on the Volume 1, Part A page. On June 12, 2024, USCIS updated the Manual to announce that it would stop applying a set of confidentiality protections, which come from 8 U.S.C. 1367, to people after they naturalize. On why no rulemaking was needed, the update points to the APA: "The Administrative Procedure Act excepts interpretive rules; general statements of policy; and rules of agency organization, procedure, or practice from notice and comment requirements." It also said USCIS delayed implementation until 30 days after publication (a later technical update gives July 12, 2024 as the effective date), and described the guidance as one that "explains and provides clarification to officers but does not add to or subtract from the statutory protections or the substantive regulations, create legally binding rights or obligations." Whatever you think of the policy, that's the path in a nutshell: an update, a short delay, new behavior at the service center.

The same log shows how small edits can sweep the whole book. On May 11, 2021, a technical update replaced "alien" with "noncitizen" throughout the Manual where possible. On February 26, 2025, another one replaced "noncitizen" with "alien." Both are listed on the same Volume 1, Part A page as technical updates touching many volumes at once. If your index keys on exact phrases, a sweep like that moves hundreds of paragraphs overnight.

Corpus mechanics

The Policy Manual is one of 53 named sources inside a federal agency guidance corpus of 96,966 sections. Two filters isolate it, and the corpus types reference lists the tokens.

Base URL is https://api.vaquill.ai/api/v1. Auth is a bearer token. Search costs 4 credits per call.

curl -X POST https://api.vaquill.ai/api/v1/us/statutes/search \
  -H "Authorization: Bearer vq_key_..." \
  -H "Content-Type: application/json" \
  -d '{
    "query": "continuous residence requirement naturalization absences",
    "corpusType": "AGENCY_GUIDANCE",
    "source": "uscis_policy_manual",
    "matchType": "any",
    "limit": 10,
    "excerptChars": 600
  }'

We ran this request on 12 October 2026 through our MCP client, which sends the same parameters (with limit 3 and excerptChars 300). The top hit, trimmed to the fields that matter here:

{
  "actId": "USCIS_PM_V12_PD_C3",
  "citation": "USCIS Policy Manual, Vol. 12, Pt. D, Ch. 3",
  "chapterName": "Continuous Residence",
  "volume": 12,
  "part": "D",
  "source": "uscis_policy_manual",
  "actStatus": "in_force",
  "sourceUrl": "https://www.uscis.gov/policy-manual/volume-12-part-d-chapter-3"
}

Every hit carries an actId, the citation, an excerpt, and sourceUrl, the uscis.gov address of the agency's own copy of that chapter. Take the actId from the response. The API reference tells you to take ids from a response rather than build them by hand, and the section identifier reference explains why.

Then fetch the chapter:

GET /us/statutes/section/{actId}
GET /us/statutes/section/{actId}/body

Use /body (6 credits) when you are feeding a model and want the text. Use the plain form (2 credits) when you are rendering a citation card that needs the metadata and source URL.

Scoping a query to a volume

Be straight about this, because it is the first thing an integrator asks. There is no volume= parameter. The search request in the OpenAPI document takes query, corpusType, state, code, article, titleNumber, chapter, part, source, agency, documentType, matchType, actStatus, excludeRepealed, changedSince, yearFrom, yearTo, publishedFrom, publishedTo, fields, limit, offset, includeBody, and excerptChars. The part and chapter filters are described as pairing with a CFR title or a state code, so we do not use them to scope the Policy Manual.

So volume scoping is done two ways, and you will probably use both. The browse hierarchy recipe covers the same shape elsewhere in the corpus.

First, put the volume in the query text. Semantic plus keyword hybrid search means the volume label in a chapter's own heading is retrievable.

{
  "query": "Volume 8 Admissibility health related grounds communicable disease",
  "corpusType": "AGENCY_GUIDANCE",
  "source": "uscis_policy_manual",
  "matchType": "any",
  "limit": 20
}

Second, filter the returned results. Each result carries an integer volume field and the citation string, so a client-side filter gives you a hard boundary that the query text alone doesn't. In our 12 October 2026 run of the query above, the top three hits were Vol. 8, Pt. B, Ch. 6 (Communicable Diseases of Public Health Significance), Ch. 1 and Ch. 2, each with volume: 8.

# results = response.json()["results"]
hits = [h for h in results if h["volume"] == 8]

That is less elegant than a server-side filter and worth saying plainly. The volume field is a documented result field, so the filter does not depend on parsing the citation text.

A third pattern for narrow work: run the sweep once, keep the actId values for the volume you care about, and re-fetch by id afterwards. A manual of roughly 460 chapters is small enough to mirror locally, which removes the scoping problem entirely.

Paging helps here. Results are cut from one ranking, so pages don't repeat or drop items between calls. limit maxes at 50 and offset at 70.

What goes wrong: the checkbox

Policy Manual chapters can decide real outcomes, and sometimes they turn on something small. Part K of Volume 8 covers the false claim to U.S. citizenship ground of inadmissibility, and it spends real time on the Form I-9, the employment eligibility form. A commenter on Hacker News described the stakes bluntly: "Accidental false claims to citizenship are a 'whoops, game over' situation which crops up on immigration advice forums from time to time" (sveiss, Hacker News, January 2020).

The manual itself is more careful than the headline. Chapter 2 of Part K says the version of the I-9 used before April 3, 2009 asked whether the person was a "citizen or national," so a "yes" there does not by itself establish a false claim to citizenship. It also lists a narrow statutory exception for certain people who reasonably believed they were citizens, and a "timely retraction" exception. And it states that "There is no waiver of inadmissibility for the false claim ground in INA 212," while noting that Congress authorized waivers for some applicants seeking adjustment of status in certain immigrant categories. USCIS posted a policy alert revising this part on August 20, 2025, so check the current text rather than a memo from last year. None of this is advice for a particular case. It is a good example of why you want the chapter, with its footnotes, and not a summary of it.

Worked example: an RFE that cites the manual

A request for evidence lands citing the Policy Manual. Here is the sequence that turns it into a checkable answer.

Step 1: resolve the chapter. Search with source=uscis_policy_manual using the language from the RFE itself, not a paraphrase. The agency's phrasing is usually lifted from the chapter, so it retrieves well.

Step 2: pull the chapter body. Fetch /section/{actId}/body, and keep the source URL from the metadata response so the attorney reviewing the output can open the agency's own page.

Step 3: reach the regulation. The chapter implements something in 8 C.F.R., so query the CFR corpus scoped to Title 8.

{
  "query": "adjustment of status eligibility to receive an immigrant visa",
  "corpusType": "CFR",
  "titleNumber": "8",
  "limit": 5
}

The CFR corpus is 222,311 sections and, per the live GET /boards registry on 12 October 2026, refreshes daily. A Title 8 search for that query returned 8 C.F.R. 245.1 (Eligibility) first.

Step 4: reach the statute. Query the USC corpus scoped to Title 8, translating the INA cite to its codified form first.

{
  "query": "adjustment of status of nonimmigrant to that of person admitted for permanent residence",
  "corpusType": "USC",
  "titleNumber": "8",
  "limit": 5
}

The USC corpus holds 60,494 sections, and each result carries a currentThrough date. For 8 U.S.C. 1255 the 12 October 2026 response gave currentThrough: 2026-09-11 and a sourceUrl on uscode.house.gov. Report that date alongside the answer, so a supervising attorney knows how current the text is.

Step 5: hand the model all three, with their source URLs. Manual chapter, regulation, statute. That is a response a reviewer can verify in three clicks instead of a summary they have to trust.

Monitoring the layer that moves

Changes we observe on a refresh become change events you can subscribe to. Call GET /boards, which costs no credits, and every watchable source comes back stamped with its cadence and its lastRetrievedAt. The USCIS Policy Manual sits on the agency_manuals board (shared with the Justice Manual, MPEP, TMEP, IRM and WHD Field Operations Handbook). On 12 October 2026 that board showed a monthly cadence, lastRetrievedAt of 2026-09-27. USCIS can publish between our refreshes, so read lastRetrievedAt before treating silence as "no change", and use USCIS's own updates log when the date matters.

From there you can create a watch, list the changes it captured, and pull a per-section diff to see what text moved. For an immigration practice the high-value watches are narrow rather than broad, since watching every chapter produces noise.

What this corpus is not

The honest boundary list, because building on a wrong assumption here is expensive.

• Not BIA decisions. Board of Immigration Appeals precedent decisions are adjudications, not guidance. They are not part of source=uscis_policy_manual. The API carries BIA precedent, Attorney General immigration decisions and legacy INS and USCIS administrative decisions in a separate AGENCY_ADJUDICATION corpus (source=bia_precedent, ag_precedent, immigration_admin_precedent), with no good-law verdict attached.
• Not court case law. Federal circuit court immigration opinions aren't here.
• Not Federal Register immigration rules. Proposed and final DHS rules live in a separate corpus, corpusType=FEDERAL_REGISTER, covering more than 196,000 sections from 1994 to the present. Query that one for rulemaking, this one for policy.
• Not the Foreign Affairs Manual. Consular processing guidance belongs to the State Department, which is a different agency with a different manual.
• Not case status or receipt data. Nothing about an individual filing is in a corpus of published guidance.

If your product needs BIA precedent, query the adjudication corpus separately. If your product needs to know what an officer is instructed to do before issuing an RFE, this source is the one.

FAQ

Is the USCIS Policy Manual legally binding?

USCIS says the Manual "is to be followed by all USCIS officers in the performance of their duties" and also that it "does not create any substantive or procedural right or benefit that is legally enforceable by any party." It is agency policy rather than a statute or a regulation, so cite the statute and regulation for what the law requires. In practice it is the most reliable predictor of what a service center will do with a filing.

Did the Policy Manual replace the Adjudicator's Field Manual?

Largely. USCIS retired the Adjudicator's Field Manual in May 2020 and is moving its content into the Policy Manual. Where the two conflict, USCIS says the Policy Manual prevails. Remaining AFM content sits as PDFs under the matching Policy Manual part, and USCIS publishes a crosswalk, so remap AFM cites in an internal knowledge base against it.

How do you cite a section of the USCIS Policy Manual?

By volume, part, and chapter, in that order: "USCIS Policy Manual, Vol. 12, Pt. D, Ch. 3". USCIS's own pages abbreviate the same address as "12 USCIS-PM D.3". The addressable unit is a chapter, so there is no single section number the way there is for 8 U.S.C. 1255. The part element is a letter, which is what breaks schemas built for numeric section keys.

Why does the Policy Manual change faster than 8 C.F.R.?

Because it changes by policy update rather than by rulemaking. Amending 8 C.F.R. requires the notice-and-comment process, which runs through a proposed rule, a comment period, and a final rule. USCIS can issue a Policy Manual update on its own, so guidance can shift while the regulation stays fixed.

How many volumes and chapters are there?

Twelve volumes. USCIS's table of contents listed 459 chapter pages in 100 parts on 12 October 2026, and that number changes as USCIS adds chapters. Volumes cover benefit families and cross-cutting topics, parts subdivide a volume, and chapters carry the text.

Can I filter a search to one volume?

Not with a dedicated parameter, because there is no volume= filter. Scope by putting the volume label into the query text, then filter the results client-side on the integer volume field. For narrow work, mirror the chapter index locally once and re-fetch by actId.

Are BIA decisions included?

Not in the Policy Manual source. The Board of Immigration Appeals issues adjudicative decisions, which are a different kind of authority from published agency guidance. The API carries BIA precedent decisions in its separate AGENCY_ADJUDICATION corpus (source=bia_precedent). Circuit court immigration opinions are not in the API.

How quickly does a new policy update reach the API?

A Policy Manual update is picked up on the refresh of its board. On 12 October 2026 the live GET /boards registry listed the agency_manuals board, which carries the Policy Manual, at a monthly cadence, with the last retrieval on 2026-09-27. The 8 C.F.R. layer underneath it refreshes daily on its own board. Read lastRetrievedAt on the board before assuming a very recent USCIS update is in the index.

Can I query the Policy Manual as it read on a past date?

Approximately. A chapter is stored at its current text, and asOf=YYYY-MM-DD on the body endpoint rebuilds an earlier version from the changes we observed after your date. The response carries an asOf block with isBounded, which tells you whether the answer rests on when capture began, and source: "unavailable" when it cannot rebuild the text. Amendment history, a currency filter and diffs on watched sources fill in the rest, and a version you must prove should be confirmed against the agency's own archive of policy updates.

What do I do about INA versus 8 U.S.C. citation forms?

Normalize in both directions before you query. Attorneys write INA 245 and INA 212(a); the corpus is keyed on the codified forms, 8 U.S.C. 1255 and 8 U.S.C. 1182(a). An extractor that handles only one form silently loses every citation written in the other.

Where to start

Call the coverage endpoint (no credits, API key required), then run one scoped search against source=uscis_policy_manual using text lifted verbatim from an RFE you already have on file. The agency's own phrasing retrieves well, so you will know quickly whether the results are good enough to build on.

Priyansh Khodiyar

Co-Founder & CTO

Priyansh leads engineering and AI at Vaquill AI: the pipelines that pull statutes, regulations and court rules from every US jurisdiction's official publisher, and the REST API, MCP server and open dataset that serve them.