https://api.sandbase.ai/v1/api/vaquill/resolveResolve up to 50 Bluebook citation strings to the exact US law sections they name.
Your output will appear here
Complete the inputs, then click Run.
Resolve up to 50 Bluebook citation strings to the exact US law sections they name.
Start building
Platform API endpoint with unified authentication and usage tracking.
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
-X POST "https://api.sandbase.ai/v1/api/vaquill/resolve" \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @- <<'SANDBASE_JSON'
{
"citations": [
"42 U.S.C. 1983"
]
}
SANDBASE_JSON
)
printf '%s\n' "$result"Set your SandBase API key in your server environment. Requests use Bearer authentication.
export SANDBASE_API_KEY="YOUR_API_KEY"Keep your key on the server. Do not expose it in browser code.
citationsarrayrequiredBluebook citations to resolve, e.g. ['42 U.S.C. 1983', '16 C.F.R. 444.1', 'Cal. Civ. Code 1950.5']. Duplicates are collapsed; at most 50 distinct citations per call. A pinpoint such as '42 U.S.C. 1983(b)(2)' resolves to the parent section and is echoed back in subsection.
statestringLowercase two-letter jurisdiction to resolve the whole batch within, for forms several states share ('8 CCR 1206-2' is Colorado, '22 CCR 76227' California). Omit for a batch that spans jurisdictions.
Possible values: al, ak, az, ar, ca, co, ct, de, dc, fl, ga, hi, id, il, in, ia, ks, ky, la, me, md, ma, mi, mn, ms, mo, mt, ne, nv, nh, nj, nm, ny, nc, nd, oh, ok, or, pa, pr, ri, sc, sd, tn, tx, ut, vt, va, wa, wv, wi, wy
corpusTypestringCorpus to resolve the whole batch within: STATE (statutory text), REGULATION (administrative codes), STATE_RULES (court rules), CONSTITUTION / STATE_CONSTITUTION.
Possible values: CONSTITUTION, REGULATION, STATE, STATE_CONSTITUTION, STATE_RULES
Saved example response for this API; no live request is made when viewing it.
No saved response has been published. Run the API in Playground to inspect its response.
Explore more
| API | Price | Response |
|---|---|---|
Vaquill ResolveThis API Vaquill | From $0.02 per call | Async JSON |
Vaquill | $0.01 per call | Async JSON |
Vaquill | From $0 per call | Async JSON |
Vaquill | $0.01 per call | Async JSON |
Questions
Send a POST request to https://api.sandbase.ai/v1/api/vaquill/resolve with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.
From $0.02 per call, billed from your SandBase balance. You are only charged for calls you make; there is no subscription.
Required: citations (array). Optional: state (one of al, ak, az, ar, ca, co, ct, de, dc, fl, ga, hi, id, il, in, ia, ks, ky, la, me, md, ma, mi, mn, ms, mo, mt, ne, nv, nh, nj, nm, ny, nc, nd, oh, ok, or, pa, pr, ri, sc, sd, tn, tx, ut, vt, va, wa, wv, wi, wy) and corpusType (one of CONSTITUTION, REGULATION, STATE, STATE_CONSTITUTION, STATE_RULES). The Parameters table and the Playground on this page list every field.
A JSON result. This endpoint runs asynchronously, so the response tells you how to fetch the finished result.
No. Vaquill Resolve runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Vaquill API access separately.