Discover/jrdz API
live

jrdz APIjrdz.dev

Access Jonathan Rodriguez's full developer CV, portfolio projects, work history, skills, certifications, and tech blog posts via 3 structured API endpoints.

This API takes change requests — .
Endpoint health
verified 4h ago
get_post
get_profile
list_posts
2/3 passing latest checkself-healing
Endpoints
3
Updated
5h ago

What is the jrdz API?

The jrdz.dev API exposes 3 endpoints covering the complete professional profile and blog content from Jonathan Rodriguez's developer portfolio. The get_profile endpoint returns over ten structured fields including work experience, certifications, projects, and technical skills. Blog content is accessible via list_posts for filtered summaries and get_post for full article text. Both English and Spanish locales are supported across all endpoints.

This call costs1 credit / call— charged only on success
Try it
Language locale for the profile content.
api.parse.bot/scraper/3cc76d40-88b5-421b-a583-e20ad73c9398/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/3cc76d40-88b5-421b-a583-e20ad73c9398/get_profile?lang=en' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace jrdz-dev-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: jrdz_dev_api SDK — bounded, re-runnable; every call capped."""
from parse_apis.jrdz_dev_api import Jrdz, Lang, Category, PostNotFound

client = Jrdz()

# Fetch the developer profile
profile = client.profiles.get(lang=Lang.EN)
print(profile.name, profile.title)
print(profile.location)
for proj in profile.projects[:3]:
    print(proj.title, proj.technologies)

# List blog posts filtered by category
for post in client.posts.list(category=Category.CLOUD, limit=3):
    print(post.title, post.pub_date)

# Get full article content using a slug derived from the post listing
first_post = client.posts.list(limit=1).first()
if first_post:
    slug = first_post.link.replace("https://jrdz.dev/", "").rstrip("/")
    try:
        article = client.articles.get(slug=slug)
        print(article.title, article.pub_date)
        print(article.content[:100])
    except PostNotFound as e:
        print(f"not found: {e.slug}")

print("exercised: profiles.get / posts.list / articles.get")
All endpoints · 3 totalmissing one? ·

Returns the full professional profile/CV including personal info, about summary, projects, work experience, education, certifications, and skills. Supports English and Spanish locales.

Input
ParamTypeDescription
langstringLanguage locale for the profile content.
Response
{
  "type": "object",
  "fields": {
    "name": "Full name of the developer",
    "about": "Professional summary paragraph",
    "title": "Professional title",
    "location": "Geographic location",
    "projects": "Array of portfolio projects with title, url, description, and technologies",
    "education": "Array of educational entries with institution, degree, and period",
    "soft_skills": "Array of soft skill names",
    "certifications": "Array of professional certifications with title, issuer, credential_id, and year",
    "work_experience": "Array of work positions with company, role, period, responsibilities, and technologies",
    "technical_skills": "Array of technical skill names"
  },
  "sample": {
    "data": {
      "name": "Jonathan Rodriguez",
      "about": "DevOps and Software Engineer with 3+ years of IT experience...",
      "title": "DevOps Engineer & Software Engineer",
      "location": "La Libertad, El Salvador",
      "projects": [
        {
          "url": "https://azmvsupport.vercel.app",
          "title": "Azure Resource Move Support",
          "description": "Tool to check Azure resource move support across regions and subscriptions",
          "technologies": [
            "TypeScript",
            "Svelte",
            "Vercel",
            "Bulma CSS"
          ]
        }
      ],
      "education": [
        {
          "degree": "Software Engineering",
          "period": "2022 - 2024",
          "institution": "ITCA FEPADE Santa Tecla"
        }
      ],
      "soft_skills": [
        "Communication",
        "Teamwork",
        "Problem Solving"
      ],
      "certifications": [
        {
          "url": "https://learn.microsoft.com/en-us/users/jrdz/credentials/63eb8b4305fa1a14",
          "year": "2025",
          "title": "Microsoft Certified: Azure Fundamentals (AZ-900)",
          "issuer": "Microsoft",
          "credential_id": "63EB8B4305FA1A14"
        }
      ],
      "work_experience": [
        {
          "role": "DevOps Engineer",
          "period": "November 2025 - Present",
          "company": "Banco Agricola El Salvador",
          "company_url": "https://www.bancoagricola.com",
          "description": "Developing and maintaining CI/CD pipelines...",
          "technologies": [
            "AWS",
            "Docker",
            "Kubernetes"
          ],
          "responsibilities": [
            "Implement DevSecOps security and compliance across CI/CD pipelines."
          ]
        }
      ],
      "technical_skills": [
        "Linux",
        "Bash Scripting",
        "Docker",
        "Kubernetes",
        "Terraform"
      ]
    },
    "status": "success"
  }
}

About the jrdz API

Profile and CV Data

The get_profile endpoint returns a structured CV-style document including name, title, location, about summary, work_experience (with company, role, period, responsibilities, and technologies per entry), education (institution, degree, period), certifications (title, issuer, credential_id, year), technical_skills, and soft_skills. The optional lang parameter switches the response content between English and Spanish locales.

Blog Post Listing and Filtering

The list_posts endpoint returns an array of post summaries from the site's blog, each including title, link, description, publication date, and category tags. The total field in the response reflects the count after filtering. You can narrow results using the lang parameter for language and the category parameter (a slug string) to filter by topic. Omitting category returns all posts across all subjects.

Full Post Content

The get_post endpoint fetches the complete text of a single article by its URL path slug, such as cloud/azure/fundamentals. The response includes title, content (full article text), pub_date in ISO 8601 format, tags (an array of category and topic labels), and the canonical url. The blog/ prefix is appended automatically if omitted from the slug input.

Reliability & maintenanceVerified

The jrdz API is a managed, monitored endpoint for jrdz.dev — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when jrdz.dev changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official jrdz.dev API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
4h ago
Latest check
2/3 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a personal portfolio mirror site pulling live CV data from get_profile including projects and work history.
  • Display Jonathan's certifications and their issuers on a resume aggregator using the certifications field.
  • Retrieve Spanish-language blog posts with list_posts using the lang parameter for a Spanish-speaking audience.
  • Fetch full article content from get_post to index jrdz.dev blog posts in a personal knowledge base or search tool.
  • Filter tech blog posts by category slug via list_posts to surface only cloud or backend-related articles.
  • Pull technical_skills and soft_skills fields to populate a developer skill comparison or tagging system.
  • Aggregate publication dates and tags from blog posts to build a chronological content timeline.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does jrdz.dev have an official developer API?+
No, jrdz.dev does not publish an official public developer API. This Parse API provides structured programmatic access to the portfolio and blog content on the site.
What does `get_profile` return for work experience entries?+
Each entry in the work_experience array includes the company name, role title, period (date range), an array of responsibilities, and an array of technologies used in that position. The lang parameter controls whether text fields are returned in English or Spanish.
Can I filter blog posts by both language and category at the same time?+
Yes. list_posts accepts both lang and category as independent optional parameters, so you can pass both together to narrow results to a specific language and category slug simultaneously. The response total field reflects the filtered count.
Does the API expose comments or engagement data for blog posts?+
Not currently. The API covers post content, tags, publication dates, and category metadata via get_post and list_posts, but does not return comment counts, view counts, or reader engagement signals. You can fork this API on Parse and revise it to add an endpoint targeting that data if it becomes available on the site.
Is pagination supported for blog post listings?+
The list_posts endpoint returns all matching posts in a single response along with a total count. There are no page or offset parameters currently exposed. You can fork this API on Parse and revise it to add pagination parameters for large result sets.
Page content last updated . Spec covers 3 endpoints from jrdz.dev.
Related APIs in B2b DirectorySee all →
anything.com API
Retrieve blog posts and organize them by category from Anything.com's AI app builder platform. Use this to access detailed content about AI development, tutorials, and platform updates directly from their official blog.
a16zcrypto.com API
Access a16z Crypto's latest blog posts, portfolio companies, and team member information with powerful search and filtering capabilities. Get comprehensive details about their investments, team profiles, and company insights all in one place.
juejin.cn API
Browse Juejin’s recommended article feed, search articles by keyword, and fetch full article details (including markdown/HTML content) by article ID.
insights.trendforce.com API
Access semiconductor and AI industry analysis articles from TrendForce Insights, browsing post listings and retrieving full article content organized into text sections and figures. Perfect for staying updated on tech industry trends and feeding structured article data into language models for analysis.
chirojobs.com API
Search and browse chiropractic job listings with detailed information, explore job categories, and access ChiroJobs blog content and pricing—all in one place. Find related positions, compare opportunities, and stay informed with the latest industry insights.
oneleet.com API
Access data from oneleet.com.
resumes.fyi API
Browse and retrieve real resumes from top tech companies that successfully passed resume screens, filtering by role, level, company, school, and verification status. Access resume data and images from over 1,884+ verified resumes to study what works for landing jobs at elite tech firms.
jobs.lever.co API
Access job postings on any Lever-hosted company job board. List, filter, search, and group open roles, retrieve full posting details, and extract application form questions via Lever's public API.