Batch geocodes and validates Brazilian 8-digit postal codes (CEPs) via official Brazilian postal & IBGE registries. Extracts Latitude/Longitude, 7-digit IBGE city code (for NF-e/CT-e), state UF, neighborhood, and Last-Mile Delivery Scores (0-100). ### Enterprise B2B Value Proposition (Brazil CEP Geocoordinates, IBGE Code & Logistics Auditor) - **Target B2B Buyers:** eCommerce Checkout Flows, Last-Mile Delivery Routers, NF-e Issuers, and Retail Omni-Channel ERPs. - **Zero External API Keys Required:** Connects directly to authoritative government, regulatory, and financial primary registries with built-in retry/backoff and deterministic schema normalization. - **Quantitative Scoring & RAG Briefs:** Every record is enriched with a quantitative 0-100 risk/viability score and an LLM-ready Markdown executive brief (`Brazil CEP Geocoordinates & IBGE City Code Audited`). - **Backend Proxy Secret Injection:** RapidAPI Studio and Zyla API Hub inject `Authorization: Bearer <TOKEN_REDACTED>` invisibly at the proxy layer when forwarding synchronous calls to `https://api.apify.com/v2/acts/b2b-quant-apis~brazil-cep-geocoordinates-logistics-auditor/run-sync-get-dataset-items`. - **Marketplace Categories:** RapidAPI `Logistics` | Zyla API Hub `Logistics & Shipping`. - **Subscription Tiers (USD):** `BASIC` ($0.00/mo, 15 req/mo hard cap), `PRO` ($19.00/mo, 1,000 req/mo + $0.02/extra), `ULTRA` ($49.00/mo, 5,000 req/mo + $0.015/extra), `MEGA` ($149.00/mo, 25,000 req/mo + $0.010/extra). - **SEO Keywords:** brazil-cep-lookup, postal-geocoding, ibge-municipality-code, nfe-address-validator, last-mile-logistics, ddd-lookup, ecommerce-checkout.
Batch geocodes and validates Brazilian 8-digit postal codes (CEPs) via official Brazilian postal & IBGE registries. Extracts Latitude/Longitude, 7-digit IBGE city code (for NF-e/CT-e), state UF, neighborhood, and Last-Mile Delivery Scores (0-100). ### Enterprise B2B Value Proposition (Brazil CEP Geocoordinates, IBGE Code & Logistics Auditor) - **Target B2B Buyers:** eCommerce Checkout Flows, Last-Mile Delivery Routers, NF-e Issuers, and Retail Omni-Channel ERPs. - **Zero External API Keys Required:** Connects directly to authoritative government, regulatory, and financial primary registries with built-in retry/backoff and deterministic schema normalization. - **Quantitative Scoring & RAG Briefs:** Every record is enriched with a quantitative 0-100 risk/viability score and an LLM-ready Markdown executive brief (`Brazil CEP Geocoordinates & IBGE City Code Audited`). - **Backend Proxy Secret Injection:** RapidAPI Studio and Zyla API Hub inject `Authorization: Bearer <TOKEN_REDACTED>` invisibly at the proxy layer when forwarding synchronous calls to `https://api.apify.com/v2/acts/b2b-quant-apis~brazil-cep-geocoordinates-logistics-auditor/run-sync-get-dataset-items`. - **Marketplace Categories:** RapidAPI `Logistics` | Zyla API Hub `Logistics & Shipping`. - **Subscription Tiers (USD):** `BASIC` ($0.00/mo, 15 req/mo hard cap), `PRO` ($19.00/mo, 1,000 req/mo + $0.02/extra), `ULTRA` ($49.00/mo, 5,000 req/mo + $0.015/extra), `MEGA` ($149.00/mo, 25,000 req/mo + $0.010/extra). - **SEO Keywords:** brazil-cep-lookup, postal-geocoding, ibge-municipality-code, nfe-address-validator, last-mile-logistics, ddd-lookup, ecommerce-checkout.
Every transaction executed by brazil-cep-geocoordinates-logistics-auditor produces verifiable event envelopes designed for high-stakes regulatory auditing, ERP master data synchronization, and automated continuous compliance workflows.
Detailed specification of data contracts, domain types, and primary source semantics enforced by brazil-cep-geocoordinates-logistics-auditor:
ceps (string) • RequiredComma-separated Brazilian postal codes (e.g., '01310100, 20040002, 30140071').
maxResults (integer) • OptionalMaximum number of CEP records to return (1 to 100).
cep (string)Standardized 8-digit Brazilian postal code.
stateUf (string)Two-letter Brazilian state code.
cityName (string)Official municipality name.
neighborhood (string)District or neighborhood.
street (string)Street address.
ibgeCityCode (string)Official 7-digit IBGE municipality code for NF-e/CT-e.
latitude (number)WGS84 Latitude coordinate.
longitude (number)WGS84 Longitude coordinate.
logisticsReadinessScore (integer)Quantitative score for last-mile routing and tax invoice completeness (0-100).
markdownLogisticsDossier (string)Executive report for e-commerce, TMS/WMS, and ERP tax engines.
Stateless payload attributes validated by JSON Schema and OpenAPI 3.0.3 standards for brazil-cep-geocoordinates-logistics-auditor.
| Field | Type | Requirement | Description & Audit Rules |
|---|---|---|---|
ceps | string | Required | Comma-separated Brazilian postal codes (e.g., '01310100, 20040002, 30140071'). |
maxResults | integer | Optional | Maximum number of CEP records to return (1 to 100). |
Primary attributes returned in the audit response envelope with cryptographic audit metadata for brazil-cep-geocoordinates-logistics-auditor.
| Attribute | Type | Definition & Source Verifiability |
|---|---|---|
cep | string | Standardized 8-digit Brazilian postal code. |
stateUf | string | Two-letter Brazilian state code. |
cityName | string | Official municipality name. |
neighborhood | string | District or neighborhood. |
street | string | Street address. |
ibgeCityCode | string | Official 7-digit IBGE municipality code for NF-e/CT-e. |
latitude | number | WGS84 Latitude coordinate. |
longitude | number | WGS84 Longitude coordinate. |
logisticsReadinessScore | integer | Quantitative score for last-mile routing and tax invoice completeness (0-100). |
markdownLogisticsDossier | string | Executive report for e-commerce, TMS/WMS, and ERP tax engines. |
Edit parameters in the request payload below and click Execute Sandbox Request to inspect the verified live schema response and dynamic cURL command.
curl -X POST "https://jesleytassili-glitch.github.io/v1/execute" \
-H "Content-Type: application/json" \
-H "X-RapidAPI-Key: YOUR_API_KEY" \
-d '{
"ceps": "01310100,20040002,30140071",
"maxResults": 5
}'
{
"cep": "01310100",
"stateUf": "SP",
"cityName": "São Paulo",
"neighborhood": "Bela Vista",
"street": "Avenida Paulista",
"ibgeCityCode": "3550308",
"latitude": -23.5475,
"longitude": -46.63611,
"logisticsReadinessScore": 100,
"markdownLogisticsDossier": "# BRAZIL CEP GEOCOORDINATES & NF-e LOGISTICS DOSSIER: 01310100\n\n## 1. Standardized Address & Tax Jurisdiction\n- **CEP (8 Digits):** `01310100`\n- **Municipality / State UF:** **São Paulo - SP**\n- **IBGE 7-Digit City Code (NF-e/CT-e):** `3550308`\n- **Neighborhood:** `Bela Vista`\n- **Street / Logradouro:** Avenida Paulista\n\n## 2. Last-Mile Geocoordinates & Readiness\n- **Logistics & NF-e Readiness Score:** **100/100**\n- **WGS84 Coordinates:** `(-23.5475, -46.63611)`"
}
Direct extraction captured from primary government or corporate registry endpoints for brazil-cep-geocoordinates-logistics-auditor.
{
"cep": "01310100",
"stateUf": "SP",
"cityName": "São Paulo",
"neighborhood": "Bela Vista",
"street": "Avenida Paulista",
"ibgeCityCode": "3550308",
"latitude": -23.5475,
"longitude": -46.63611,
"logisticsReadinessScore": 100,
"markdownLogisticsDossier": "# BRAZIL CEP GEOCOORDINATES & NF-e LOGISTICS DOSSIER: 01310100\n\n## 1. Standardized Address & Tax Jurisdiction\n- **CEP (8 Digits):** `01310100`\n- **Municipality / State UF:** **São Paulo - SP**\n- **IBGE 7-Digit City Code (NF-e/CT-e):** `3550308`\n- **Neighborhood:** `Bela Vista`\n- **Street / Logradouro:** Avenida Paulista\n\n## 2. Last-Mile Geocoordinates & Readiness\n- **Logistics & NF-e Readiness Score:** **100/100**\n- **WGS84 Coordinates:** `(-23.5475, -46.63611)`"
}
import requests
url = "https://jesleytassili-glitch.github.io/specs_openapi_31/brazil-cep-geocoordinates-logistics-auditor.json" # Direct spec
endpoint = "https://api.apify.com/v2/acts/b2b-quant-apis~brazil-cep-geocoordinates-logistics-auditor/run-sync-get-dataset-items"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN" # RapidAPI or Apify Token
}
payload = {
"ceps": "01310100,20040002,30140071",
"maxResults": 5
}
response = requests.post(endpoint, json=payload, headers=headers, timeout=60)
print(f"Status Code: {response.status_code}")
data = response.json()
print("Audit Records Count:", len(data) if isinstance(data, list) else 1)
// Node.js 18+ Native Fetch or MCP CLI
import fetch from "node-fetch";
const payload = {
"ceps": "01310100,20040002,30140071",
"maxResults": 5
};
const response = await fetch("https://api.apify.com/v2/acts/b2b-quant-apis~brazil-cep-geocoordinates-logistics-auditor/run-sync-get-dataset-items", {
method: "POST",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer " + process.env.B2B_API_TOKEN
},
body: JSON.stringify(payload)
});
const result = await response.json();
console.log("Verified Records:", result);
// Or run directly via MCP CLI:
// npx -y b2b-compliance-mcp-cli execute --server brazil-cep-geocoordinates-logistics-auditor --payload '{"ceps": "01310100,20040002,30140071", "maxResults": 5}'
curl -X POST "https://api.apify.com/v2/acts/b2b-quant-apis~brazil-cep-geocoordinates-logistics-auditor/run-sync-get-dataset-items" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN" \
-d '{"ceps": "01310100,20040002,30140071", "maxResults": 5}'
name: Daily Compliance Audit - brazil-cep-geocoordinates-logistics-auditor
on:
schedule:
- cron: '0 8 * * 1-5' # Monday to Friday at 08:00 UTC
workflow_dispatch:
jobs:
audit:
runs-on: ubuntu-latest
steps:
- name: Trigger Audit Run
run: |
curl -f -s -X POST "https://api.apify.com/v2/acts/b2b-quant-apis~brazil-cep-geocoordinates-logistics-auditor/run-sync-get-dataset-items" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer ${{ secrets.B2B_API_TOKEN }}" \
-d '{"ceps": "01310100,20040002,30140071", "maxResults": 5}' > audit_output.json
- name: Archive Compliance Evidence
uses: actions/upload-artifact@v4
with:
name: brazil-cep-geocoordinates-logistics-auditor-evidence
path: audit_output.json
| HTTP Status | Classification | Resolution Behavior for brazil-cep-geocoordinates-logistics-auditor |
|---|---|---|
200 OK |
Success | Query executed successfully; validated Brazil CEP Geocoordinates, IBGE Code & Logistics Auditor records returned. |
400 Bad Request |
Schema Validation | Payload missing required fields or format mismatch for brazil-cep-geocoordinates-logistics-auditor; inspect JSON schema. |
401 / 403 Forbidden |
Authentication Failure | Invalid proxy API key or direct unauthorized bypass attempt for Brazil CEP Geocoordinates, IBGE Code & Logistics Auditor. |
429 Too Many Requests |
Rate Limit Exceeded | Tier limits triggered for brazil-cep-geocoordinates-logistics-auditor; inspect Retry-After response header. |
502 Upstream Resilient |
Graceful Degradation | Upstream regulatory portal offline; returns safe empty set with $0 billed fee. |
brazil-tax-reform-ncm-classtrib-auditor) • [Markdown Guide]eu-vies-vat-tax-compliance-auditor) • [Markdown Guide]brazil-antt-freight-cte-auditor) • [Markdown Guide]brazil-b2b-cnpj-qsa-lead-enricher) • [Markdown Guide]brazil-ibge-cnae-municipal-b2b-expansion-enricher) • [Markdown Guide]us-nhtsa-vehicle-vin-recall-auditor) • [Markdown Guide]us-census-fcc-real-estate-geo-enricher) • [Markdown Guide]