Blog

Why I Started Markidy: An Alternative to Scraped Data

Why I Started Markidy: An Alternative to Scraped Data

I started Markidy because I felt that the underlying data behind finding people and opportunities was far more problematic than I had expected.

There is already an enormous amount of profile, resume, portfolio, and service information online.

The problem is that the existence of data and the ability for others to use it properly from outside those platforms are two entirely different things.

In practice, there is already significant demand for automation in finding people, identifying the right targets, discovering marketing prospects, and conducting market research.

Companies want to find candidates more quickly, search more broadly, and systematize as much of that process as possible.

However, much of that data is locked inside large platforms, where external disclosure and reuse are restricted.

In that structure, the demand does not disappear.

Instead, the market addresses it through crawling, unofficial collection, third-party datasets, and the sale of data snapshots.

In fact, many companies already find people and services in exactly this way.

They purchase structured data gathered through crawling and use it to search, classify, and connect with job seekers, freelancers, influencers, and even housing listings in automated ways.

The problem begins there.

Although this data may be useful in the short term, it is often unclear whether the individual concerned actually intended it to be public.

It is frequently not synchronized with the latest information,

its source may be opaque,

and information that has already changed may continue to circulate.

In other words, there is clearly demand in the market today.

But the way that demand is currently being met is highly unstable in terms of consent, trust, freshness, and transparency.

I came to believe that this structure will become a greater problem over time.

Automation for discovering and connecting people, which was once possible only at the company level, is likely to expand gradually to a much broader range of actors.

For that shift to be possible, information about people and services cannot remain locked inside platforms or exist only in the form of human-readable introductions.

What is needed is a public layer that is structured, limited to the scope to which the person has consented, and readable and usable by external software.

As automation and AI become more widespread, I believe the need for such a layer will only grow.

If forms of automation that were once available only to companies are to become available to individuals as well, the underlying information must also be open in a way that can be trusted.

That is why I started Markidy.

Markidy is not simply a place to post a profile.

It is intended to be a public layer in which people can opt in to make themselves or their services public, where that information can be searched in structured form, and where, over time, it can also be read and used through APIs, MCP, or CLI.

The problem I want to solve is not simply that there is no place to post a profile.

The real problem is that even though a great deal of information already exists on the internet,

that information is closed,

outdated,

not controlled from the perspective of the people it describes,

or scattered in forms that software cannot readily use.

Rather than a world in which scraped snapshot data continues to circulate,

I believe that a world in which people can choose to make themselves public,

update their own information,

and exist within a public layer that machines can read

will become more important.

If clients can automate on the basis of verified data shared with consent,

instead of purchasing crawled data for automation,

that will create far more opportunity

both for those trying to find people

and for those who want to be found.

How do you see this issue?

If you have encountered similar problems, or have observed this structure directly in practice, I would be interested to hear your perspective.

All Posts