Scb Se PxWeb API
69
AI ReadinessAI-Aware (B+)69/100
Official vendor OpenAPI document · agent-readyCRMContact Managementnone12 EndpointsREST
For Agents
Programmatically list all available tables with filtering and pagination, get a specific table by identifier. Covers 12 operations.
Use for: I need to all available tables with filtering and pagination, I want to a specific table by identifier, Search for detailed metadata for a table, Find all default selection parameters for a table
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Statistics Sweden PxWebApi v2 provides access to tables, metadata, and data from the Swedish Statistical Database. Supports GET and POST methods for data retrieval with multiple output formats. The API exposes 12 endpoints.
Install Jentic One Beta
Connect the PxWeb API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PxWeb API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fscb.se%2Fscb-se" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fscb.se%2Fscb-se" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with PxWeb API.
List all available tables with filtering and pagination
Get a specific table by identifier
Fetch table data with custom filtering via POST
Create and save a query for reuse
Monitor PxWeb API operational status and events
Use Cases
Patterns agents use PxWeb API for, with concrete tasks.
★ CRM Operations
Use the PxWeb API to perform crm operations programmatically. The API provides 12 endpoints covering core functionality including list all available tables with filtering and pagination, get a specific table by identifier, get detailed metadata for a table.
Call GET /tables to list all available tables with filtering and pagination
Automated Codelists Management
Automate codelists operations by combining multiple PxWeb API endpoints. Agents can get a specific table by identifier and then get detailed metadata for a table in a single workflow.
Call GET /tables/{id} to get a specific table by identifier, then verify the result
AI Agent Integration via Jentic
AI agents discover and call PxWeb API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'list all available tables with filtering and pagination', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
12 endpoints — statistics sweden pxwebapi v2 provides access to tables, metadata, and data from the swedish statistical database.
METHOD
PATH
DESCRIPTION
GET
/tables
List all available tables with filtering and pagination
GET
/tables/{id}
Get a specific table by identifier
GET
/tables/{id}/metadata
Get detailed metadata for a table
GET
/tables/{id}/defaultselection
Get default selection parameters for a table
POST
/tables/{id}/data
Fetch table data with custom filtering via POST
GET
/tables/{id}/data
Fetch table data with custom filtering via GET
POST
/savedqueries
Create and save a query for reuse
GET
/savedqueries/{id}
Retrieve a saved query by identifier
GET
/tables
List all available tables with filtering and pagination
GET
/tables/{id}
Get a specific table by identifier
GET
/tables/{id}/metadata
Get detailed metadata for a table
GET
/tables/{id}/defaultselection
Get default selection parameters for a table
POST
/tables/{id}/data
Fetch table data with custom filtering via POST
GET
/tables/{id}/data
Fetch table data with custom filtering via GET
POST
/savedqueries
Create and save a query for reuse
GET
/savedqueries/{id}
Retrieve a saved query by identifier
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
PxWeb API
- AI-Aware (B+)69/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability100
Security61
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
35%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
61
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
61%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the PxWeb API by hand means targeting the statistikdatabasen host, walking its table metadata and default-selection endpoints, and assembling data queries yourself. Through Jentic you install once, import the PxWeb API from the API Directory, and your agent calls it.
Permission scoping
PxWeb puts the table id in the URL path (/tables/{id}), so a rule can pin your agent to one table. You choose the operations it may call, so a write like saving a query is not included unless you add it alongside the read and metadata operations.
Credential isolation
The PxWeb API endpoints take no credential, and Jentic executes the calls without placing any secret in the agent's prompt, logs, or context. Any configuration you do store is held encrypted by your own Jentic One instance and injected at execution time.
Intent-based discovery
Agents search Jentic by intent such as 'list available statistics tables' or 'fetch table data', and Jentic returns the matching PxWeb API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PxWeb API through Jentic.
What authentication does the PxWeb API use?
The PxWeb API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I list all available tables with filtering and pagination with the PxWeb API?
Yes. Use the GET /tables endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the PxWeb API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list all available tables with filtering and pagination through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all available tables with filtering and pagination'. Jentic returns the matching PxWeb API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the PxWeb API have?
The PxWeb API exposes 12 endpoints covering codelists, config, savedqueries operations.
Can I limit what my agent is allowed to do with the PxWeb API?
Yes. Because you run Jentic One yourself, your own rules decide which PxWeb API operations and configuration your agent may use. Since the table id sits in the URL path, such as GET /tables/{id} and GET /tables/{id}/metadata, you can pin the agent to a single table and grant only the read and metadata calls it needs. A write such as POST /savedqueries stays out of reach unless you explicitly add it.
GET STARTED