Avago Technologies

Avago Technologies Limited was the Singapore-headquartered semiconductor company spun out of Agilent Technologies' semiconductor products group in 2005 that acquired Broadcom Corporation for $37 billion on February 1, 2016 and renamed itself Broadcom Limited, today Broadcom Inc. (NASDAQ: AVGO). Avago is therefore not a subsidiary of Broadcom but its legal predecessor and former corporate name. The brand is retired: every path on avagotech.com returns an HTTP 301 to broadcom.com, avago.com is a third-party domain-brokerage landing page rather than a company site, and no Avago-branded developer portal, documentation, OpenAPI, SDK, package or GitHub organization exists. API surfaces once associated with Avago product lines (LSI and Emulex storage controllers, fiber optics, RF) are published today by Broadcom and are profiled under the broadcom record.

Avago Technologies is profiled on the APIs.io network. Tagged areas include Company, Semiconductors, Hardware, Electronic Components, and Acquired.

Avago Technologies’ developer surface includes engineering blog and 4 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

4.3/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-10-23 · rubric v0.25.0 · Show this score on your site →

0 APIs

Company Semiconductors Hardware Electronic Components AcquiredLegacy BrandBroadcom

Kin Score

Kin Score How this is scored →
scored 2026-10-23 · rubric v0.25.0

Composite quality — 4.3/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 0.4 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 4.4 / 9

Regulatory Posture 0.9 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/avago-technologies/"><img src="https://apis.io/badge/avago-technologies/card.svg" alt="Avago Technologies on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/avago-technologies: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Avago Technologies Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 1

Properties that don't map to a standard resource type

ParentCompany

ParentCompany

Source (apis.yml)

aid: avago-technologies
name: Avago Technologies
description: 'Avago Technologies Limited was the Singapore-headquartered semiconductor company spun out of Agilent Technologies''
  semiconductor products group in 2005 that acquired Broadcom Corporation for $37 billion on February 1, 2016 and renamed
  itself Broadcom Limited, today Broadcom Inc. (NASDAQ: AVGO). Avago is therefore not a subsidiary of Broadcom but its legal
  predecessor and former corporate name. The brand is retired: every path on avagotech.com returns an HTTP 301 to broadcom.com,
  avago.com is a third-party domain-brokerage landing page rather than a company site, and no Avago-branded developer portal,
  documentation, OpenAPI, SDK, package or GitHub organization exists. API surfaces once associated with Avago product lines
  (LSI and Emulex storage controllers, fiber optics, RF) are published today by Broadcom and are profiled under the broadcom
  record.'
url: https://raw.githubusercontent.com/api-evangelist/avago-technologies/refs/heads/main/apis.yml
specificationVersion: '0.20'
created: '2026-09-13'
modified: '2026-10-06'
tags:
- Company
- Semiconductors
- Hardware
- Electronic Components
- Acquired
- Legacy Brand
- Broadcom
x-type: company
x-source: harvest:absent-parent
x-tier: legacy-identity
x-tier-reason: renamed-to-broadcom
x-parent: broadcom
x-relationship: rename
x-renamed: 2016
common:
- url: https://www.broadcom.com/company/news
  type: Blog
- type: DomainSecurity
  url: security/avago-technologies-domain-security.yml
- type: Website
  url: https://www.avagotech.com/
  name: Avago Technologies (redirects to Broadcom)
  x-note: Blanket HTTP 301 to https://www.broadcom.com/ on every path (probed 2026-09-13).
- type: ParentCompany
  url: https://apis.io/providers/broadcom/
  name: Broadcom
  x-relationship: rename
  x-renamed: 2016
  x-source: https://investors.broadcom.com/news-releases/news-release-details/broadcom-limited-announces-expected-completion-business
- type: LLMsTxt
  url: llms/avago-technologies-llms.txt
  name: Avago Technologies llms.txt
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-09-13'
  status: minimal
  artifacts_added: 3
  pass: local-v3
x-coverage:
  state: none
  reason: defunct
  detail: 'Avago Technologies Limited renamed itself Broadcom Limited on 1 February 2016 after acquiring Broadcom Corporation,
    so the brand has no surface of its own: every path on avagotech.com returns an HTTP 301 to broadcom.com, avago.com is
    a third-party domain-brokerage landing page, and no Avago GitHub organization, developer portal, package or machine-readable
    contract exists.'
  evidence:
  - url: https://www.avagotech.com/
    status: 301
  - url: https://www.avagotech.com/openapi.json
    status: 301
  - url: https://www.avagotech.com/.well-known/agent-card.json
    status: 301
  - url: https://api.github.com/orgs/avagotech
    status: 404
  - url: https://avago.com/
    status: 200
  checked: '2026-09-13'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/avago-technologies"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/avago-technologies/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/avago-technologies/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.