careof
Find and parse postal addresses in HTML, Markdown, and plain text.
careof turns a document into a ranked list of addresses with components, confidence, and provenance. It is built for contact pages, footers, business listings, and pages where the address is buried in prose.
Named after the postal convention: care of.
import careof
for address in careof.extract(html, "text/html", country="ph"):
print(address.raw)
print(address.components)
$ careof examples/contact.html --country ph --language en
[
{
"raw": "123 Mabini Street, Makati City, Metro Manila 1223, PH",
"components": {
"house_number": "123",
"road": "Mabini Street",
"city": "Makati City",
"state": "Metro Manila",
"postcode": "1223",
"country": "PH"
},
"confidence": 0.99,
"key": "123 mabini street makati city metro manila 1223 ph",
"sources": [{ "kind": "json-ld", "score": 0.99 }]
}
]
(The populated components come from libpostal; without it the same address is returned with "components": {}.)
Status
Alpha. The pipeline, adapters, structured-data path, deduplication, and CLI are implemented and tested. GLiNER and libpostal are optional: without them you still get structured matches and regex-backed extraction, just with empty component dicts.
Install
pip install careof
Optional model:
pip install "careof[model]" # gliner + torch
Optional URL fetching:
pip install "careof[fetch]" # httpx, used by the careof-url command
Optional parser:
pip install "careof[postal]" # ctypes bindings...
...and the system library it binds to, which pip cannot install:
git clone https://github.com/openvenues/libpostal
cd libpostal
./bootstrap.sh
./configure --datadir=/usr/local/share/libpostal
make -j"$(nproc)"
sudo make install
sudo ldconfig
Alternatively, connect to a libpostal REST service such as oozman/libpostal-rest. No local postal bindings are needed for HTTP mode:
careof page.html --country at --language de \
--libpostal-url http://127.0.0.1:8080
Set CAREOF_LIBPOSTAL_URL to use the service by default with the CLI. The REST adapter calls POST /parser for components and POST /expand for deduplication keys. Without either a local installation or a configured REST service, careof still returns raw address strings but leaves components empty.
Python version
Core supports Python 3.10–3.13. pyre2-updated currently provides wheels through Python 3.13; Python 3.14 is not supported yet. For the model extra, prefer 3.12 or 3.13. careof does not depend on spaCy.
Usage
Python
import careof
addresses = careof.extract(
source, # str or bytes
content_type=None, # detected from the source, URL, or suffix
url=None,
language="en",
country="ph",
libpostal_url=None, # e.g. "http://127.0.0.1:8080" for REST mode
threshold=0.4, # GLiNER span threshold
extractor="auto", # "auto" | "gliner" | "heuristic" | None
parser=None, # local bindings by default; set libpostal_url for REST
structured=True, # use JSON-LD, microdata, <address>, og:*, maps links
)
extractor=None returns only structured matches. That is the cheapest mode and a good default for crawling at scale.
from careof.parse import NullParser
addresses = careof.extract(html, "text/html", parser=NullParser())
Or pass a REST URL directly:
addresses = careof.extract(
html,
"text/html",
language="de",
country="at",
libpostal_url="http://127.0.0.1:8080",
)
CLI
careof page.html
careof contact.md --country ph
careof page.html --country at --language de --libpostal-url http://127.0.0.1:8080
cat page.html | careof - --content-type text/html
careof page.html --extractor heuristic --ndjson
The REST URL can also be set once with export CAREOF_LIBPOSTAL_URL=http://127.0.0.1:8080.
To fetch a page directly by URL, install the optional fetch extra and use the separate command:
pip install "careof[fetch]"
careof-url https://example.com/contact --country us --extractor heuristic
careof-url follows redirects, uses the response content type, and defaults to a 20-second timeout and 10 MiB response limit. Override these with --timeout and --max-bytes.
--extractor none keeps only structured matches. JSON is pretty-printed by default; --ndjson emits one object per line.
Output
Address.to_dict() returns:
| Field | Meaning |
|---|---|
raw |
The address string as found, whitespace-normalised |
components |
libpostal-style labels (house_number, road, unit, city, state, postcode, country, ...) |
confidence |
Heuristic 0–0.99 score; structured sources rank highest |
key |
Normalised dedupe key (libpostal expansion when available) |
sources |
Every place the address was seen: kind, document offsets, block index, model score |
HTML offsets refer to careof's normalised text, not the original HTML byte stream. Markdown masking preserves offsets exactly, so those line up with the source file.
How it works
- Adapters —
lxmlparses HTML; a block-aware serializer puts newlines at block boundaries so<br>and<div>do not glue street and city together. Markdown and plain text are split into paragraphs. Code fences and inline code are masked with spaces, preserving offsets. - Structured signals — JSON-LD
PostalAddress, microdata,<address>,og:street-address& friends, and Google/Apple Maps links are collected first. These are cheap and more reliable than any model. - Candidates —
re2finds house-number + street-suffix patterns, PO boxes, postal codes, and English landmark phrases, then keeps a few hundred characters of context. Country-name signals are generated frompycountry's ISO catalog, with common aliases such asUSAandUK. - Extraction — GLiNER runs only on those windows, chunked with overlap. The no-model fallback uses the same patterns to return line-level spans.
- Parsing — libpostal parses each candidate and
expand_addresssupplies the dedupe key. - Merge — exact keys, then conservative token-subset matching; components and provenance are combined and results are ranked.
auto uses GLiNER when the model extra is installed. The first call downloads the checkpoint (about 500 MB); pass extractor="heuristic" or extractor=None if you do not want that.
Design notes
lxml, not BeautifulSoup. Real parsing, real error recovery, and no extra layer between the document and the offsets.pyre2-updated(re2), notre. Untrusted pages cannot cause catastrophic backtracking. Fallback to Python'sreengine is disabled. The trade-off is no backreferences or lookaround, which the patterns avoid.- GLiNER directly, not
gliner_spacy. No spaCy dependency, no stale wrapper, and spans come back as character offsets. - libpostal is a parser, not an extractor. It expects an address, so it runs after candidate extraction, never on a whole page.
- Structured data wins ties. A JSON-LD
PostalAddressoutranks anything the model produces.
Limitations
- No geocoding. This extracts text, it does not resolve coordinates.
- libpostal's coverage and component quality vary by country. Pass
countryandlanguagehints when you know them. - Duplicate detection is text-based. Two genuinely different addresses can share a key, and two spellings of the same address can stay separate when libpostal is absent.
- The HTML serializer normalises text; use
sourcesfor the derived offsets, not as byte offsets into the original response.
Releasing
The version lives in one place: src/careof/_version.py.
# 1. Update _version.py and CHANGELOG.md, then:
python -m build
twine check dist/*
# 2. Tag the release; CI publishes to PyPI via Trusted Publishing.
git tag v0.1.1
git push origin v0.1.1
One-time setup on PyPI: add a trusted publisher at
https://pypi.org/manage/account/publishing/ with:
- project:
careof - owner/repository: your GitHub account and repo
- workflow:
publish.yml - environment:
pypi
No API token is stored in GitHub. To rehearse first, upload manually to TestPyPI:
python -m twine upload --repository testpypi dist/*
Development
python3 -m venv .venv
.venv/bin/pip install -e ".[dev]"
.venv/bin/pytest
.venv/bin/ruff check src tests
License
MIT
Metadata
Release files for careof 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| careof-0.1.1.tar.gz | 39.5 kB | With provenance | Details for careof-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| careof-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for careof-0.1.1-py3-none-any.whl |
Total release size: 72.4 kB
Release files / careof-0.1.1.tar.gz
| Download URL | careof-0.1.1.tar.gz |
|---|---|
| Size | 39.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c930ec58e6d2164a986e39237f57c4d351c84abfa20e7424fe3f3e6b1e04fd7e
|
|
BLAKE2b-256 checksum How to use checksums |
76fc376a6425b816f93605308fd78f9cff21801bc4ac4f09d9759bba84727171
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / careof-0.1.1-py3-none-any.whl
| Download URL | careof-0.1.1-py3-none-any.whl |
|---|---|
| Size | 32.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3998e8ff0c05d913214879c9987e61e8d548032a694e14aae7dcd96aa4fd153b
|
|
BLAKE2b-256 checksum How to use checksums |
f43f21a940972f64efb6d715fb1824bf44a078a54dbe8ce0e3b044a1495ac53c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logSecurity for careof 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for careof-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.