Opposition · USPTO

Opposition 91245764

OtherUSPTO

Opposition 91245764 at USPTO between Intel Corporation and Bryan Zamudio, over the mark AGINTEL, filed Jan 10, 2019. Status in the office record: other.

View AGINTELGet this data via the API
Status
Other
Result
Other
Filed
Jan 10, 2019
Marks involved
34
Parties

Who is involved

The parties as named in the office record.

Opponent

Intel Corporation

Company trademarks
Respondent

Bryan Zamudio

Timeline

How the case has moved

Dates from the USPTO record and the AGINTEL filing.

  1. AGINTEL filed

    Application 88019135 filed at the USPTO.

  2. Opposition filed

    Intel Corporation started opposition 91245764 at USPTO against AGINTEL.
Marks

Marks involved

1 contested mark, 33 marks the challenger relies on.

MarkRoleApplicationOffice
AGINTELContested88019135USPTO
INTELRelied on72384319USPTO
INTELRelied on72384320USPTO
INTELRelied on73035122USPTO
INTEL INSIDERelied on74159673USPTO
INTELRelied on74225506USPTO
INTELRelied on74225623USPTO
INTEL INSIDERelied on75160103USPTO
INTELRelied on75160105USPTO
INTELRelied on75160106USPTO
INTELRelied on75163576USPTO
INTELRelied on75349837USPTO

+22 more marks in this case

API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

Get API keyView docs
GET /v1/proceedings/{id}
ID=prc_734a127b-e36d-46ba-bf29-62e14a7d144a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_734a127b-e36d-46ba-bf29-62e14a7d144a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91245764",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-01-10",
  "parties": [
    {
      "name": "Intel Corporation",
      "role": "opponent"
    },
    {
      "name": "Bryan Zamudio",
      "role": "respondent"
    }
  ]
}